| /Linux-v6.1/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_IOMEM 6 /* virtio ioMemory */
38 #define VIRTIO_ID_RPMSG 7 /* virtio remote processor messaging */
39 #define VIRTIO_ID_SCSI 8 /* virtio scsi */
40 #define VIRTIO_ID_9P 9 /* 9p virtio console */
[all …]
|
| /Linux-v6.1/drivers/virtio/ |
| D | Kconfig | 5 config VIRTIO config
9 This option is selected by any driver which implements the virtio
24 Legacy PCI device (Virtio PCI Card 0.9.x Draft and older device)
31 bool "Virtio drivers"
37 bool "Harden virtio notification"
51 tristate "PCI driver for virtio devices"
54 select VIRTIO
56 This driver provides support for virtio based paravirtual device
58 virtio backends. Most QEMU based VMMs should support these devices
64 bool "Support for legacy virtio draft 0.9.X and older devices"
[all …]
|
| D | virtio_pci_legacy_dev.c | 10 * vp_legacy_probe: probe the legacy virtio pci device, note that the
12 * @ldev: the legacy virtio-pci device
33 * The virtio ring base address is expressed as a 32-bit PFN, in vp_legacy_probe()
43 rc = pci_request_region(pci_dev, 0, "virtio-pci-legacy"); in vp_legacy_probe()
66 * vp_legacy_probe: remove and cleanup the legacy virtio pci device
67 * @ldev: the legacy virtio-pci device
80 * @ldev: the legacy virtio-pci device
93 * @ldev: the legacy virtio-pci device
105 * @ldev: the legacy virtio-pci device
117 * @ldev: the legacy virtio-pci device
[all …]
|
| D | virtio_pci_modern_dev.c | 9 * vp_modern_map_capability - map a part of virtio pci capability
10 * @mdev: the modern virtio-pci device
87 "virtio_pci: map virtio %zu@%u " in vp_modern_map_capability()
97 "virtio_pci: unable to map virtio %u@%u on bar %i\n", in vp_modern_map_capability()
209 * vp_modern_probe: probe the modern virtio pci device, note that the
211 * @mdev: the modern virtio-pci device
230 * virtio device id, same as legacy driver always did. in vp_modern_probe()
278 "virtio-pci-modern"); in vp_modern_probe()
355 * vp_modern_remove: remove and cleanup the modern virtio pci device
356 * @mdev: the modern virtio-pci device
[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
|
| /Linux-v6.1/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-v6.1/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-v6.1/Documentation/devicetree/bindings/virtio/ |
| D | virtio-device.yaml | 4 $id: http://devicetree.org/schemas/virtio/virtio-device.yaml#
7 title: Virtio device bindings
13 These bindings are applicable to virtio devices irrespective of the bus they
16 # We need a select here so we don't match all nodes with 'virtio,mmio'
19 pattern: "^virtio,device[0-9a-f]{1,8}$"
20 description: Virtio device nodes.
21 "virtio,deviceID", where ID is the virtio device id. The textual
32 virtio@3000 {
33 compatible = "virtio,mmio";
38 compatible = "virtio,device22";
|
| D | mmio.yaml | 4 $id: http://devicetree.org/schemas/virtio/mmio.yaml#
7 title: virtio memory mapped devices
13 See https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio for
18 const: virtio,mmio
29 description: Required when the node corresponds to a virtio-iommu device.
50 virtio@3000 {
51 compatible = "virtio,mmio";
60 compatible = "virtio,mmio";
|
| /Linux-v6.1/Documentation/devicetree/bindings/i2c/ |
| D | i2c-virtio.yaml | 4 $id: http://devicetree.org/schemas/i2c/i2c-virtio.yaml#
7 title: Virtio I2C Adapter
14 - $ref: /schemas/virtio/virtio-device.yaml#
17 Virtio I2C device, see /schemas/virtio/virtio-device.yaml for more details.
24 const: virtio,device22
33 virtio@3000 {
34 compatible = "virtio,mmio";
39 compatible = "virtio,device22";
|
| /Linux-v6.1/Documentation/devicetree/bindings/gpio/ |
| D | gpio-virtio.yaml | 4 $id: http://devicetree.org/schemas/gpio/gpio-virtio.yaml#
7 title: Virtio GPIO controller
13 - $ref: /schemas/virtio/virtio-device.yaml#
16 Virtio GPIO controller, see /schemas/virtio/virtio-device.yaml for more
24 const: virtio,device29
45 virtio@3000 {
46 compatible = "virtio,mmio";
51 compatible = "virtio,device29";
|
| /Linux-v6.1/sound/virtio/ |
| D | virtio_card.h | 3 * virtio-snd: Virtio sound device
10 #include <linux/virtio.h>
17 #define VIRTIO_SND_CARD_DRIVER "virtio-snd"
18 #define VIRTIO_SND_CARD_NAME "VirtIO SoundCard"
19 #define VIRTIO_SND_PCM_NAME "VirtIO PCM"
35 * struct virtio_snd - VirtIO sound card device.
36 * @vdev: Underlying virtio device.
41 * @pcm_list: VirtIO PCM device list.
42 * @jacks: VirtIO jacks.
44 * @substreams: VirtIO PCM substreams.
[all …]
|
| D | virtio_pcm.h | 3 * virtio-snd: Virtio sound device
17 * struct virtio_pcm_substream - VirtIO PCM substream.
18 * @snd: VirtIO sound device.
22 * @features: Stream VirtIO feature bit map (1 << VIRTIO_SND_PCM_F_XXX).
66 * struct virtio_pcm_stream - VirtIO PCM stream.
67 * @substreams: VirtIO substreams belonging to the stream.
80 * struct virtio_pcm - VirtIO PCM device.
81 * @list: VirtIO PCM list entry.
84 * @streams: VirtIO PCM streams (playback and capture).
|
| D | virtio_card.c | 3 * virtio-snd: Virtio sound device
50 * @snd: VirtIO sound device.
51 * @event: VirtIO sound event.
102 * @snd: VirtIO sound device.
158 * @snd: VirtIO sound device.
172 * @snd: VirtIO sound device.
194 * @snd: VirtIO sound device.
261 * @vdev: VirtIO parent device.
292 * @vdev: VirtIO parent device.
336 * virtsnd_remove() - Remove VirtIO and ALSA devices.
[all …]
|
| D | virtio_jack.c | 3 * virtio-snd: Virtio sound device
23 * struct virtio_jack - VirtIO jack.
26 * @features: Jack virtio feature bit map (1 << VIRTIO_SND_JACK_F_XXX).
44 * @vjack: VirtIO jack.
92 * @vjack: VirtIO jack.
124 * @snd: VirtIO sound device.
174 * @snd: VirtIO sound device.
206 * @snd: VirtIO sound device.
207 * @event: VirtIO sound event.
|
| /Linux-v6.1/drivers/firmware/arm_scmi/ |
| D | Kconfig | 97 bool "SCMI transport based on VirtIO"
98 depends on VIRTIO=y || VIRTIO=ARM_SCMI_PROTOCOL
102 This enables the virtio based transport for SCMI.
105 transport based on VirtIO, answer Y.
108 bool "SCMI VirtIO transport Version 1 compliance"
112 This enforces strict compliance with VirtIO Version 1 specification.
114 If you want the ARM SCMI VirtIO transport layer to refuse to work
115 with Legacy VirtIO backends and instead support only VirtIO Version 1
118 If you want instead to support also old Legacy VirtIO backends (like
119 the ones implemented by kvmtool) and let the core Kernel VirtIO layer
[all …]
|
| /Linux-v6.1/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-v6.1/drivers/i2c/busses/ |
| D | i2c-virtio.c | 3 * Virtio I2C Bus Driver
5 * The Virtio I2C Specification:
6 * https://raw.githubusercontent.com/oasis-tcs/virtio-spec/master/virtio-i2c.tex
17 #include <linux/virtio.h>
23 * struct virtio_i2c - virtio I2C data
24 * @vdev: virtio device for this controller
26 * @vq: the virtio virtqueue for communication
35 * struct virtio_i2c_req - the virtio I2C request structure
36 * @completion: completion of virtio I2C message
37 * @out_hdr: the OUT header of the virtio I2C message
[all …]
|
| /Linux-v6.1/Documentation/virt/kvm/s390/ |
| 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-v6.1/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
159 context, which will look for virtio devices supported by the rproc's
162 If found, those virtio devices will be created and added, so as a result
163 of registering this remote processor, additional virtio drivers might get
212 handlers. If rpmsg/virtio functionality is also desired, then the ->kick handler
258 supported virtio devices (and their configurations).
[all …]
|
| /Linux-v6.1/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-v6.1/arch/arm64/boot/dts/arm/ |
| D | rtsm_ve-motherboard-rs2.dtsi | 13 virtio@140000 {
14 compatible = "virtio,mmio";
19 virtio@150000 {
20 compatible = "virtio,mmio";
25 virtio@200000 {
26 compatible = "virtio,mmio";
|
| /Linux-v6.1/Documentation/networking/ |
| D | net_failover.rst | 28 virtio-net accelerated datapath: STANDBY mode
31 net_failover enables hypervisor controlled accelerated datapath to virtio-net
35 feature on the virtio-net interface and assign the same MAC address to both
36 virtio-net and VF interfaces.
45 <model type='virtio'/>
59 In this configuration, the first device definition is for the virtio-net
63 virtio-net device is set to 'down' to ensure that the 'failover' netdev prefers
64 the VF passthrough device for normal communication. The virtio-net device will
70 points to the alias name declared for the virtio-net device.
88 virtio-net interface, and ens11 is the slave 'primary' VF passthrough interface.
[all …]
|
| /Linux-v6.1/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-v6.1/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
118 * @vq: virtio queue activity was received on
121 * on the virtio channel - most likely a response to request we
152 /* Wakeup if anyone waiting for VirtIO ring space. */ in req_done()
193 /* We don't currently allow canceling of virtio requests */
264 p9_debug(P9_DEBUG_TRANS, "9p debug: virtio request\n"); in p9_virtio_request()
[all …]
|
