| /linux-5.10/drivers/virtio/ |
| D | Kconfig | 2 config VIRTIO config
5 This option is selected by any driver which implements the virtio
16 bool "Virtio drivers"
22 tristate "PCI driver for virtio devices"
24 select VIRTIO
26 This driver provides support for virtio based paravirtual device
28 virtio backends. Most QEMU based VMMs should support these devices
34 bool "Support for legacy virtio draft 0.9.X and older devices"
38 Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
41 both devices conforming to Virtio 1 specification, and legacy devices.
[all …]
|
| D | virtio_dma_buf.c | 3 * dma-bufs for virtio exported objects
12 * virtio_dma_buf_export - Creates a new dma-buf for a virtio exported object
16 * This wraps dma_buf_export() to allow virtio drivers to create a dma-buf
17 * for an virtio exported object that can be queried by other virtio drivers
38 * virtio_dma_buf_attach - mandatory attach callback for virtio dma-bufs
58 * is_virtio_dma_buf - returns true if the given dma-buf is a virtio dma-buf
68 * virtio_dma_buf_get_uuid - gets a virtio dma-buf's exported object's uuid
|
| D | virtio_pci_legacy.c | 3 * Virtio PCI driver - legacy device support
5 * This module allows virtio devices to be used over a virtual PCI device.
19 /* virtio config->get_features() implementation */
29 /* virtio config->finalize_features() implementation */
46 /* virtio config->get() implementation */
147 "platform bug: legacy virtio-mmio must not be used with RAM above 0x%llxGB\n", in setup_vq()
232 * The virtio ring base address is expressed as a 32-bit PFN, in virtio_pci_legacy_probe()
242 rc = pci_request_region(pci_dev, 0, "virtio-pci-legacy"); in virtio_pci_legacy_probe()
253 /* we use the subsystem vendor/device id as the virtio vendor/device in virtio_pci_legacy_probe()
255 * virtio devices and to identify the particular virtio driver by in virtio_pci_legacy_probe()
|
| D | virtio_mmio.c | 3 * Virtio memory mapped device driver
7 * This module allows virtio devices to be used over a virtual, memory mapped
15 * .name = "virtio-mmio",
34 * compatible = "virtio,mmio";
52 * Based on Virtio PCI driver by Anthony Liguori, copyright IBM Corp. 2007
55 #define pr_fmt(fmt) "virtio-mmio: " fmt
67 #include <linux/virtio.h>
132 …dev_err(&vdev->dev, "New virtio-mmio devices (version 2) must provide VIRTIO_F_VERSION_1 feature!\… in vm_finalize_features()
399 * virtio-mmio v1 uses a 32bit QUEUE PFN. If we have something in vm_setup_vq()
405 "platform bug: legacy virtio-mmio must not be used with RAM above 0x%llxGB\n", in vm_setup_vq()
[all …]
|
| /linux-5.10/tools/virtio/virtio-trace/ |
| D | README | 1 Trace Agent for virtio-trace
7 - splice the page from write_pipe to virtio-console without memory copying
19 write the data to virtio-serial.
28 Makefile: Makefile of trace agent for virtio-trace
38 To use this trace agent for virtio-trace, we need to prepare some virtio-serial
42 virtio-trace uses virtio-serial pipe as trace data paths as to the number
44 # mkdir /tmp/virtio-trace/
45 # mkfifo /tmp/virtio-trace/trace-path-cpu{0,1,2,...,X}.{in,out}
46 # mkfifo /tmp/virtio-trace/agent-ctl-path.{in,out}
53 2) Set up of virtio-serial pipe in a host
[all …]
|
| /linux-5.10/include/uapi/linux/ |
| D | virtio_ids.h | 4 * Virtio IDs
32 #define VIRTIO_ID_NET 1 /* virtio net */
33 #define VIRTIO_ID_BLOCK 2 /* virtio block */
34 #define VIRTIO_ID_CONSOLE 3 /* virtio console */
35 #define VIRTIO_ID_RNG 4 /* virtio rng */
36 #define VIRTIO_ID_BALLOON 5 /* virtio balloon */
37 #define VIRTIO_ID_RPMSG 7 /* virtio remote processor messaging */
38 #define VIRTIO_ID_SCSI 8 /* virtio scsi */
39 #define VIRTIO_ID_9P 9 /* 9p virtio console */
40 #define VIRTIO_ID_RPROC_SERIAL 11 /* virtio remoteproc serial link */
[all …]
|
| D | virtio_mem.h | 3 * Virtio Mem Device
47 * Each virtio-mem device manages a dedicated region in physical address
49 * for a single NUMA node are possible. A virtio-mem device is like a
54 * Virtio-mem devices can only operate on their assigned memory region in
86 /* --- virtio-mem: feature bits --- */
92 /* --- virtio-mem: guest -> host requests --- */
133 /* --- virtio-mem: host -> guest response --- */
184 /* --- virtio-mem: configuration --- */
|
| D | vhost.h | 4 /* Userspace interface for in-kernel virtio accelerators. */
6 /* vhost is used to reduce the number of system calls involved in virtio.
8 * Existing virtio net code is used in the guest without modification.
102 /* Attach virtio net ring to a raw socket, or tap device.
126 * the device id defined in virtio-spec.
130 * of the device status defined in virtio-spec.
135 * definition of the device config defined in virtio-spec.
|
| /linux-5.10/drivers/crypto/virtio/ |
| D | virtio_crypto_mgr.c | 2 /* Management for virtio crypto devices (refer to adf_dev_mgr.c)
26 * @vcrypto_dev: Pointer to virtio crypto device.
28 * Function adds virtio crypto device to the global list.
29 * To be used by virtio crypto device specific drivers.
69 * @vcrypto_dev: Pointer to virtio crypto device.
71 * Function removes virtio crypto device from the acceleration framework.
72 * To be used by virtio crypto device specific drivers.
87 * Function returns the first virtio crypto device from the acceleration
90 * To be used by virtio crypto device specific drivers.
109 * @vcrypto_dev: Pointer to virtio crypto device.
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/virtio/ |
| D | mmio.txt | 1 * virtio memory mapped device
3 See https://ozlabs.org/~rusty/virtio-spec/ for more details.
7 - compatible: "virtio,mmio" compatibility string
11 Required properties for virtio-iommu:
13 - #iommu-cells: When the node corresponds to a virtio-iommu device, it is
16 "iommus" property. For virtio-iommu #iommu-cells must be
22 have an "iommus" property [1]. Since virtio-iommu itself
23 does not access memory through an IOMMU, the "virtio,mmio"
30 compatible = "virtio,mmio";
39 compatible = "virtio,mmio";
|
| D | iommu.txt | 1 * virtio IOMMU PCI device
3 When virtio-iommu uses the PCI transport, its programming interface is
6 masters. Therefore, the PCI root complex that hosts the virtio-iommu
11 - compatible: Should be "virtio,pci-iommu"
20 For virtio-iommu, #iommu-cells must be 1.
25 virtio-iommu node doesn't have an "iommus" property, and is omitted from
36 compatible = "virtio,pci-iommu";
|
| /linux-5.10/Documentation/virt/kvm/ |
| D | s390-diag.rst | 38 DIAGNOSE function code 'X'500' - KVM virtio functions
41 If the function code specifies 0x500, various virtio-related functions
44 General register 1 contains the virtio subfunction code. Supported
45 virtio subfunctions depend on KVM's userspace. Generally, userspace
46 provides either s390-virtio (subcodes 0-2) or virtio-ccw (subcode 3).
52 Subcode 0 - s390-virtio notification and early console printk
55 Subcode 1 - s390-virtio reset
58 Subcode 2 - s390-virtio set status
61 Subcode 3 - virtio-ccw notification
65 the subchannel of the virtio-ccw proxy device to be notified.
[all …]
|
| /linux-5.10/arch/arc/boot/dts/ |
| D | haps_hs.dts | 69 virtio0: virtio@f0100000 {
70 compatible = "virtio,mmio";
75 virtio1: virtio@f0102000 {
76 compatible = "virtio,mmio";
81 virtio2: virtio@f0104000 {
82 compatible = "virtio,mmio";
87 virtio3: virtio@f0106000 {
88 compatible = "virtio,mmio";
93 virtio4: virtio@f0108000 {
94 compatible = "virtio,mmio";
|
| /linux-5.10/Documentation/staging/ |
| D | remoteproc.rst | 20 duplicated. In addition, this framework also adds rpmsg virtio devices
24 (for more information about the virtio-based rpmsg bus and its drivers,
26 Registration of other types of virtio devices is now also possible. Firmwares
27 just need to publish what kind of virtio devices do they support, and then
29 existing virtio drivers with remote processor backends at a minimal development
158 context, which will look for virtio devices supported by the rproc's
161 If found, those virtio devices will be created and added, so as a result
162 of registering this remote processor, additional virtio drivers might get
211 handlers. If rpmsg/virtio functionality is also desired, then the ->kick handler
257 supported virtio devices (and their configurations).
[all …]
|
| /linux-5.10/Documentation/filesystems/ |
| D | virtiofs.rst | 6 virtiofs: virtio-fs host<->guest shared file system
14 VIRTIO "virtio-fs" device for guest<->host file system sharing. It allows a
24 expose the storage network to the guest. The virtio-fs device was designed to
27 Furthermore the virtio-fs device takes advantage of the co-location of the
39 Please see https://virtio-fs.gitlab.io/ for details on how to configure QEMU
58 Since the virtio-fs device uses the FUSE protocol for file system requests, the
62 with the virtio-fs device interface.
75 the virtio-fs device uses a "hiprio" virtqueue specifically for requests that
|
| /linux-5.10/drivers/vhost/ |
| D | Kconfig | 14 the host side of a virtio ring.
30 tristate "Host kernel accelerator for virtio net"
48 for use with virtio-scsi guests
51 tristate "vhost virtio-vsock driver"
59 virtio_transport.ko driver loaded to use the virtio-vsock device.
72 guest virtio devices with the vDPA-based backends.
82 ordering from host while using legacy virtio.
|
| /linux-5.10/net/9p/ |
| D | trans_virtio.c | 3 * The Virtio 9p transport driver
10 * Based on virtio console driver
35 #include <linux/virtio.h>
51 * @vdev: virtio dev associated with this channel
52 * @vq: virtio queue associated with this channel
114 * @vq: virtio queue activity was received on
117 * on the virtio channel - most likely a response to request we
148 /* Wakeup if anyone waiting for VirtIO ring space. */ in req_done()
189 /* We don't currently allow canceling of virtio requests */
259 p9_debug(P9_DEBUG_TRANS, "9p debug: virtio request\n"); in p9_virtio_request()
[all …]
|
| /linux-5.10/fs/fuse/ |
| D | Kconfig | 32 tristate "Virtio Filesystem"
34 select VIRTIO
36 The Virtio Filesystem allows guests to mount file systems from the
43 bool "Virtio Filesystem Direct Host Memory Access support"
53 If you want to allow mounting a Virtio Filesystem with the "dax"
|
| /linux-5.10/arch/arm64/boot/dts/arm/ |
| D | rtsm_ve-motherboard-rs2.dtsi | 13 virtio-p9@140000 {
14 compatible = "virtio,mmio";
19 virtio-net@150000 {
20 compatible = "virtio,mmio";
|
| /linux-5.10/drivers/nvdimm/ |
| D | virtio_pmem.h | 3 * virtio_pmem.h: virtio pmem Driver
6 * from host and provides a virtio based flushing
35 /* Virtio pmem request queue */
38 /* nvdimm bus registers virtio pmem device */
|
| D | virtio_pmem.c | 3 * virtio_pmem.c: Virtio pmem Driver
57 dev_err(&vdev->dev, "failed to initialize virtio pmem vq's\n"); in virtio_pmem_probe()
68 vpmem->nd_desc.provider_name = "virtio-pmem"; in virtio_pmem_probe()
120 MODULE_DEVICE_TABLE(virtio, id_table);
121 MODULE_DESCRIPTION("Virtio pmem driver");
|
| /linux-5.10/tools/include/uapi/linux/ |
| D | vhost.h | 4 /* Userspace interface for in-kernel virtio accelerators. */
6 /* vhost is used to reduce the number of system calls involved in virtio.
8 * Existing virtio net code is used in the guest without modification.
102 /* Attach virtio net ring to a raw socket, or tap device.
126 * the device id defined in virtio-spec.
130 * of the device status defined in virtio-spec.
135 * definition of the device config defined in virtio-spec.
|
| /linux-5.10/include/linux/ |
| D | virtio_ring.h | 10 * Barriers in virtio are tricky. Non-SMP virtio guests can't assume
12 * barriers. Non-SMP virtio hosts could skip the barriers, but does
19 * For using virtio to talk to real devices (eg. other heterogeneous
21 * kinds of virtio, so it's a runtime decision, and the branch is
|
| /linux-5.10/block/ |
| D | blk-mq-virtio.c | 7 #include <linux/blk-mq-virtio.h>
13 * blk_mq_virtio_map_queues - provide a default queue mapping for virtio device
15 * @vdev: virtio device to provide a mapping for.
18 * This function assumes the virtio device @vdev has at least as many available
|
| /linux-5.10/Documentation/translations/zh_CN/filesystems/ |
| D | virtiofs.rst | 15 virtiofs: virtio-fs 主机<->客机共享文件系统
22 Linux的virtiofs文件系统实现了一个半虚拟化VIRTIO类型“virtio-fs”设备的驱动，通过该\
43 请查阅 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守护程序的详细信息。
56 其关键，因为此时不可能加入高优先级的请求。为了解决此差异，virtio-fs设备采用“hiprio”\
|