| /kernel/linux/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
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-4.19/drivers/virtio/ |
| D | Kconfig | 1 config VIRTIO config
4 This option is selected by any driver which implements the virtio
9 bool "Virtio drivers"
15 tristate "PCI driver for virtio devices"
17 select VIRTIO
19 This driver provides support for virtio based paravirtual device
21 virtio backends. Most QEMU based VMMs should support these devices
27 bool "Support for legacy virtio draft 0.9.X and older devices"
31 Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
34 both devices conforming to Virtio 1 specification, and legacy devices.
[all …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-4.19/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 | mic_common.h | 30 * struct mic_device_desc: Virtio device information shared between the
31 * virtio driver and userspace backend
51 * struct mic_device_ctrl: Per virtio device information in the device page
56 * @vdev_reset: Set to 1 by guest to indicate virtio device has been reset.
76 * struct mic_bootparam: Virtio device independent information in device page
79 * @h2c_config_db: Host to Card Virtio config doorbell set by card
101 * @desc: Array of MIC virtio device descriptors.
111 * @address: Guest/MIC physical address of the virtio ring
142 * - virtio device config space
161 * @vr: The virtio ring.
|
| D | mic_ioctl.h | 28 * mic_copy - MIC virtio descriptor copy.
35 * the virtio device.
50 * Add a new virtio device
52 * for the virtio device consisting of:
56 * - virtio device config space
69 * Notify virtio device of a config change
|
| /kernel/linux/linux-4.19/drivers/crypto/virtio/ |
| D | virtio_crypto_mgr.c | 1 /* Management for virtio crypto devices (refer to adf_dev_mgr.c)
38 * @vcrypto_dev: Pointer to virtio crypto device.
40 * Function adds virtio crypto device to the global list.
41 * To be used by virtio crypto device specific drivers.
81 * @vcrypto_dev: Pointer to virtio crypto device.
83 * Function removes virtio crypto device from the acceleration framework.
84 * To be used by virtio crypto device specific drivers.
99 * Function returns the first virtio crypto device from the acceleration
102 * To be used by virtio crypto device specific drivers.
121 * @vcrypto_dev: Pointer to virtio crypto device.
[all …]
|
| /kernel/linux/linux-4.19/drivers/misc/mic/vop/ |
| D | vop_main.h | 18 * Intel Virtio Over PCIe (VOP) driver.
26 #include <linux/virtio.h>
41 * obey the virtio spec according to which guest works with native
53 * @hotplug_work: Handle virtio device creation, deletion and configuration
54 * @cookie: Cookie received upon requesting a virtio configuration interrupt
56 * @vdev_list: List of "active" virtio devices injected in the peer node
58 * creation/deletion of virtio devices on the peer node
80 * struct vop_vringh - Virtio ring host information.
91 * @vdev: Back pointer to VOP virtio device for vringh_notify(..).
106 * struct vop_vdev - Host information for a card Virtio device.
[all …]
|
| /kernel/linux/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";
|
| /kernel/linux/linux-4.19/Documentation/virtual/kvm/ |
| D | s390-diag.txt | 35 DIAGNOSE function code 'X'500' - KVM virtio functions
38 If the function code specifies 0x500, various virtio-related functions
41 General register 1 contains the virtio subfunction code. Supported
42 virtio subfunctions depend on KVM's userspace. Generally, userspace
43 provides either s390-virtio (subcodes 0-2) or virtio-ccw (subcode 3).
49 Subcode 0 - s390-virtio notification and early console printk
52 Subcode 1 - s390-virtio reset
55 Subcode 2 - s390-virtio set status
58 Subcode 3 - virtio-ccw notification
62 the subchannel of the virtio-ccw proxy device to be notified.
[all …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/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";
|
| /kernel/linux/linux-4.19/Documentation/mic/ |
| D | mic_overview.txt | 17 leverages the standard virtio framework for network, disk and console
18 devices, though in our case the virtio framework is used across a PCIe
19 bus. A Virtio Over PCIe (VOP) driver allows creating user space
20 backends or devices on the host which are used to probe virtio drivers
22 in the kernel is used to access virtio rings from the host. The card
23 VOP driver allows card virtio drivers to communicate with their user
25 can add, remove and configure virtio devices. A thin MIC specific
34 and used only by the host driver to transfer data for the virtio devices.
45 virtio backends are situated on the host rather than the card given better
48 the fact that the virtio block storage backend can only be on the host.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | remoteproc.txt | 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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/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
|
| /kernel/linux/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.
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-4.19/net/9p/ |
| D | trans_virtio.c | 2 * The Virtio 9p transport driver
9 * Based on virtio console driver
50 #include <linux/virtio.h>
66 * @vdev: virtio dev associated with this channel
67 * @vq: virtio queue associated with this channel
129 * @vq: virtio queue activity was received on
132 * on the virtio channel - most likely a response to request we
163 /* Wakeup if anyone waiting for VirtIO ring space. */ in req_done()
204 /* We don't currently allow canceling of virtio requests */
274 p9_debug(P9_DEBUG_TRANS, "9p debug: virtio request\n"); in p9_virtio_request()
[all …]
|
| /kernel/linux/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"
|