| /kernel/linux/linux-6.6/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 …]
|
| /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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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-6.6/Documentation/driver-api/virtio/ |
| D | virtio.rst | 6 Virtio on Linux
12 Virtio is an open standard that defines a protocol for communication
14 Types") of the virtio spec (`[1]`_). Originally developed as a standard
20 devices provided by the hypervisor, which exposes them as virtio devices
27 Although the virtio devices are really an abstraction layer in the
30 orthogonal to the device itself. The virtio spec defines these transport
35 the hypervisor is done through shared memory (that's what makes virtio
46 Refer to Chapter 2.5 ("Virtqueues") of the virtio spec (`[1]`_) for the
47 reference definitions of virtqueues and "Virtqueues and virtio ring: How
54 ultimately used by virtio drivers:
[all …]
|
| D | writing_virtio_drivers.rst | 6 Writing Virtio Drivers
13 need to hack a new virtio driver or understand the essentials of the
14 existing ones. See :ref:`Virtio on Linux <virtio>` for a general
15 overview of virtio.
21 As a bare minimum, a virtio driver needs to register in the virtio bus
27 #include <linux/virtio.h>
107 MODULE_DEVICE_TABLE(virtio, id_table);
108 MODULE_DESCRIPTION("Dummy virtio driver");
111 The device id ``VIRTIO_ID_DUMMY`` here is a placeholder, virtio drivers
114 in the virtio spec before being added to that file.
[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-6.6/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-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-6.6/Documentation/devicetree/bindings/virtio/ |
| D | virtio-device.yaml | 4 $id: http://devicetree.org/schemas/virtio/virtio-device.yaml#
7 title: Virtio device
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";
|
| /kernel/linux/linux-6.6/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";
|
| /kernel/linux/linux-6.6/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";
|
| /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";
|
| /kernel/linux/linux-6.6/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).
|
| /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-6.6/drivers/firmware/arm_scmi/ |
| D | Kconfig | 143 bool "SCMI transport based on VirtIO"
144 depends on VIRTIO=y || VIRTIO=ARM_SCMI_PROTOCOL
148 This enables the virtio based transport for SCMI.
151 transport based on VirtIO, answer Y.
154 bool "SCMI VirtIO transport Version 1 compliance"
158 This enforces strict compliance with VirtIO Version 1 specification.
160 If you want the ARM SCMI VirtIO transport layer to refuse to work
161 with Legacy VirtIO backends and instead support only VirtIO Version 1
164 If you want instead to support also old Legacy VirtIO backends (like
165 the ones implemented by kvmtool) and let the core Kernel VirtIO layer
[all …]
|
| /kernel/linux/linux-6.6/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-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-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|