| /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>
106 MODULE_DEVICE_TABLE(virtio, id_table);
107 MODULE_DESCRIPTION("Dummy virtio driver");
110 The device id ``VIRTIO_ID_DUMMY`` here is a placeholder, virtio drivers
113 in the virtio spec before being added to that file.
[all …]
|
| D | index.rst | 4 Virtio title
10 virtio
|
| /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";
|
| D | pci-iommu.yaml | 4 $id: http://devicetree.org/schemas/virtio/pci-iommu.yaml#
7 title: virtio-iommu device using the virtio-pci transport
13 When virtio-iommu uses the PCI transport, its programming interface is
16 masters. Therefore, the PCI root complex that hosts the virtio-iommu
20 virtio-iommu node doesn't have an "iommus" property, and is omitted from
30 - const: virtio,pci-iommu
|
| /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";
|
| /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";
|
| /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 …]
|
| /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
|
| D | 9p.rst | 47 For server running on QEMU host with virtio transport::
49 mount -t 9p -o trans=virtio <mount_tag> /mnt/9
52 mount points. Each 9P export is seen by the client as a virtio device with an
54 seen by reading /sys/bus/virtio/drivers/9pnet_virtio/virtio<n>/mount_tag files.
123 virtio connect to the next virtio channel available
|
| /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 …]
|
| D | rpmsg.rst | 37 Rpmsg is a virtio-based messaging bus that allows kernel drivers to communicate
82 a tx buffer and puts it back on virtio's used descriptor ring),
106 a tx buffer and puts it back on virtio's used descriptor ring),
131 a tx buffer and puts it back on virtio's used descriptor ring),
331 virtio device feature set. This feature bit means that the remote
344 The plan is also to add static creation of rpmsg channels via the virtio
|
| /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 …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-virtiofs | 3 Contact: virtio-fs@lists.linux.dev
9 Contact: virtio-fs@lists.linux.dev
11 Symlink to the virtio device that exports this filesystem.
|
| /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”\
|
| /Documentation/translations/zh_TW/filesystems/ |
| D | virtiofs.rst | 16 virtiofs: virtio-fs 主機<->客機共享文件系統
23 Linux的virtiofs文件系統實現了一個半虛擬化VIRTIO類型“virtio-fs”設備的驅動，通過該\
44 請查閱 https://virtio-fs.gitlab.io/ 瞭解配置QEMU和virtiofsd守護程序的詳細信息。
57 其關鍵，因爲此時不可能加入高優先級的請求。爲了解決此差異，virtio-fs設備採用“hiprio”\
|
| /Documentation/userspace-api/ |
| D | vduse.rst | 5 vDPA (virtio data path acceleration) device is a device that uses a
6 datapath which complies with the virtio specifications with vendor
14 Note that only virtio block device is supported by VDUSE framework now,
100 such as device name (uniquely identify a VDUSE device), virtio features, virtio
145 the virtio spec: https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html
147 status bit if the device can not accept the negotiated virtio features
|
| /Documentation/translations/zh_CN/virt/ |
| D | ne_overview.rst | 58 virtio-pci vsock模拟设备，而飞地虚拟机有virtio-mmio vsock模拟设备。vsock
60 virtio-vsock设备获得中断。virtio-mmio设备被放置在典型的4 GiB以下的内存中。
|
| /Documentation/virt/ |
| D | ne_overview.rst | 58 using virtio-vsock [5]. The primary VM has virtio-pci vsock emulated device,
59 while the enclave VM has a virtio-mmio vsock emulated device. The vsock device
61 APIC and IOAPIC - to get interrupts from virtio-vsock device. The virtio-mmio
|
| /Documentation/devicetree/bindings/mips/loongson/ |
| D | devices.yaml | 36 - description: Virtual Loongson64 Quad Core + VirtIO
38 - const: loongson,loongson64v-4core-virtio
|
| /Documentation/networking/device_drivers/ethernet/amd/ |
| D | pds_vdpa.rst | 16 a vDPA device for use by the virtio network stack. It is used with
17 the Pensando Virtual Function devices that offer vDPA and virtio queue
50 # Create a vDPA device for use in virtio network configurations
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 15 kernel for vCPU scheduling, memory management, inter-VM communication and virtio
47 mechanisms will be provided in the future based on VirtIO-vsock.
51 The solution is provided using the well-known VirtIO. The gzvm module redirects
|
| /Documentation/bpf/ |
| D | s390.rst | 137 -drive file=./s390.img,if=virtio,format=raw \
142 -device virtio-rng-ccw,rng=rng0 \
144 -device virtio-net-ccw,netdev=net0
204 - `Plan 9 folder sharing over Virtio <https://wiki.qemu.org/Documentation/9psetup>`_
|
| /Documentation/devicetree/bindings/iommu/ |
| D | xen,grant-dma.yaml | 7 title: Xen specific IOMMU for virtualized devices (e.g. virtio)
|