Home
last modified time | relevance | path

Searched refs:virtio (Results 1 – 25 of 318) sorted by relevance

12345678910>>...13

/openbmc/u-boot/doc/
H A DREADME.virtio26 device. The memory mapped virtio device behaviour is based on the PCI device
63 [*] PCI driver for virtio devices
79 -device virtio-net-device,netdev=net0 \
81 -device virtio-blk-device,drive=hd0
87 -device virtio-net-pci,netdev=net0 \
89 -device virtio-blk-pci,drive=hd0
98 -device virtio-net-pci,netdev=net0 \
100 -device virtio-blk-device,drive=hd0 \
102 -device virtio-blk-pci,drive=hd1
109 -device virtio-net-pci,netdev=net0,disable-legacy=true,disable-modern=false \
[all …]
/openbmc/linux/tools/virtio/virtio-trace/
H A DREADME1 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 …]
/openbmc/qemu/tests/qtest/libqos/
H A Dmeson.build36 'virtio.c',
37 'virtio-balloon.c',
38 'virtio-blk.c',
40 'virtio-mmio.c',
41 'virtio-net.c',
42 'virtio-pci.c',
43 'virtio-pci-modern.c',
44 'virtio-rng.c',
45 'virtio-scsi.c',
46 'virtio-serial.c',
[all …]
/openbmc/qemu/hw/virtio/
H A Dmeson.build2 system_virtio_ss.add(files('virtio-bus.c'))
3 system_virtio_ss.add(when: 'CONFIG_VIRTIO_PCI', if_true: files('virtio-pci.c'))
4 system_virtio_ss.add(when: 'CONFIG_VIRTIO_MMIO', if_true: files('virtio-mmio.c'))
5 system_virtio_ss.add(when: 'CONFIG_VIRTIO_CRYPTO', if_true: files('virtio-crypto.c'))
7 system_virtio_ss.add(when: 'CONFIG_VIRTIO_IOMMU', if_true: files('virtio-iommu.c'))
11 specific_virtio_ss.add(files('virtio.c'))
12 specific_virtio_ss.add(files('virtio-config-io.c', 'virtio-qmp.c'))
51 specific_virtio_ss.add(when: 'CONFIG_VIRTIO_BALLOON', if_true: files('virtio-balloon.c'))
53 specific_virtio_ss.add(when: 'CONFIG_VIRTIO_PMEM', if_true: files('virtio-pmem.c'))
56 specific_virtio_ss.add(when: 'CONFIG_VIRTIO_RNG', if_true: files('virtio-rng.c'))
[all …]
/openbmc/linux/Documentation/driver-api/virtio/
H A Dvirtio.rst14 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:
56 .. kernel-doc:: include/linux/virtio.h
65 .. kernel-doc:: drivers/virtio/virtio_ring.c
[all …]
H A Dwriting_virtio_drivers.rst13 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.
139 that's only the second half of the virtio device-driver communication
[all …]
/openbmc/u-boot/drivers/virtio/
H A DKconfig14 # See http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.pdf for
22 This option is selected by any driver which implements the virtio
26 bool "Platform bus driver for memory mapped virtio devices"
29 This driver provides support for memory mapped virtio
33 bool "PCI driver for virtio devices"
37 This driver provides support for virtio based paravirtual device
41 bool "Sandbox driver for virtio devices"
45 This driver provides support for Sandbox implementation of virtio
49 bool "virtio net driver"
52 This is the virtual net driver for virtio. It can be used with
[all …]
/openbmc/qemu/docs/system/devices/
H A Dvirtio-gpu.rst4 virtio-gpu
7 This document explains the setup and usage of the virtio-gpu device.
8 The virtio-gpu device paravirtualizes the GPU and display controller.
13 virtio-gpu requires a guest Linux kernel built with the
16 QEMU virtio-gpu variants
19 QEMU virtio-gpu device variants come in the following form:
21 * ``virtio-vga[-BACKEND]``
22 * ``virtio-gpu[-BACKEND][-INTERFACE]``
26 **Backends:** QEMU provides a 2D virtio-gpu backend, and two accelerated
31 **Interfaces:** QEMU further categorizes virtio-gpu device variants based
[all …]
H A Dvirtio-pmem.rst3 virtio pmem
6 This document explains the setup and usage of the virtio pmem device.
7 The virtio pmem device is a paravirtualized persistent memory device
17 How does virtio-pmem compare to the nvdimm emulation?
22 specification. The virtio pmem device provides guest write persistence
25 virtio pmem usage
28 A virtio pmem device backed by a memory-backend-file can be created on
32 -device virtio-pmem-pci,memdev=mem1,id=nv1
39 - "device virtio-pmem-pci,id=nvdimm1,memdev=mem1" creates a virtio pmem
42 Multiple virtio pmem devices can be created if multiple pairs of "-object"
[all …]
H A Dvirtio-snd.rst1 virtio sound
33 Add an audio device and an audio backend at once with ``-audio`` and ``model=virtio``:
35 * pulseaudio: ``-audio driver=pa,model=virtio``
36 or ``-audio driver=pa,model=virtio,server=/run/user/1000/pulse/native``
37 * sdl: ``-audio driver=sdl,model=virtio``
38 * coreaudio: ``-audio driver=coreaudio,model=virtio``
48 -device virtio-sound-pci,audiodev=my_audiodev \
/openbmc/qemu/hw/s390x/
H A Dmeson.build15 's390-virtio-hcall.c',
31 s390x_ss.add(when: 'CONFIG_S390_CCW_VIRTIO', if_true: files('s390-virtio-ccw.c'))
36 virtio_ss.add(files('virtio-ccw.c'))
37 virtio_ss.add(when: 'CONFIG_VIRTIO_BALLOON', if_true: files('virtio-ccw-balloon.c'))
38 virtio_ss.add(when: 'CONFIG_VIRTIO_BLK', if_true: files('virtio-ccw-blk.c'))
39 virtio_ss.add(when: 'CONFIG_VIRTIO_CRYPTO', if_true: files('virtio-ccw-crypto.c'))
40 virtio_ss.add(when: 'CONFIG_VIRTIO_INPUT', if_true: files('virtio-ccw-input.c'))
41 virtio_ss.add(when: 'CONFIG_VIRTIO_NET', if_true: files('virtio-ccw-net.c'))
42 virtio_ss.add(when: 'CONFIG_VIRTIO_RNG', if_true: files('virtio-ccw-rng.c'))
43 virtio_ss.add(when: 'CONFIG_VIRTIO_SCSI', if_true: files('virtio-ccw-scsi.c'))
[all …]
/openbmc/qemu/hw/display/
H A Dmeson.build36 system_ss.add(when: 'CONFIG_VIRTIO', if_true: files('virtio-dmabuf.c'))
68 if_true: [files('virtio-gpu-base.c', 'virtio-gpu.c'), pixman])
70 virtio_gpu_ss.add(files('virtio-gpu-udmabuf.c'))
72 virtio_gpu_ss.add(files('virtio-gpu-udmabuf-stubs.c'))
75 hw_display_modules += {'virtio-gpu': virtio_gpu_ss}
80 if_true: [files('virtio-gpu-gl.c', 'virtio-gpu-virgl.c'), pixman, virgl])
81 hw_display_modules += {'virtio-gpu-gl': virtio_gpu_gl_ss}
87 if_true: [files('virtio-gpu-rutabaga.c'), pixman])
88 hw_display_modules += {'virtio-gpu-rutabaga': virtio_gpu_rutabaga_ss}
95 if_true: [files('virtio-gpu-pci.c'), pixman])
[all …]
/openbmc/linux/arch/arc/boot/dts/
H A Dhaps_hs.dts69 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";
/openbmc/linux/drivers/virtio/
H A DKconfig9 This option is selected by any driver which implements the virtio
37 bool "Harden virtio notification"
51 tristate "PCI driver for virtio devices"
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"
77 so, you can happily disable this option and virtio will not
84 tristate "vDPA driver for virtio devices"
88 This driver provides support for virtio based paravirtual
91 physical device to allow the datapath of virtio to be
[all …]
/openbmc/linux/Documentation/translations/zh_CN/filesystems/
H A Dvirtiofs.rst15 virtiofs: virtio-fs 主机<->客机共享文件系统
22 Linux的virtiofs文件系统实现了一个半虚拟化VIRTIO类型“virtio-fs”设备的驱动，通过该\
29 步骤，且将存储网络暴露给客机。而virtio-fs设备通过提供不经过网络的文件系统访问文件\
43 请查阅 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守护程序的详细信息。
47 由于virtio-fs设备将FUSE协议用于文件系统请求，因此Linux的virtiofs文件系统与FUSE文\
49 间之间的/dev/fuse接口由virtio-fs设备接口代替。
56 其关键，因为此时不可能加入高优先级的请求。为了解决此差异，virtio-fs设备采用“hiprio”\
/openbmc/linux/arch/arm64/boot/dts/arm/
H A Drtsm_ve-motherboard-rs2.dtsi13 virtio@140000 {
14 compatible = "virtio,mmio";
19 virtio@150000 {
20 compatible = "virtio,mmio";
25 virtio@200000 {
26 compatible = "virtio,mmio";
/openbmc/qemu/docs/devel/migration/
H A Dvirtio.rst10 Saving and restoring the state of virtio devices is a bit of a twisty maze,
15 - virtio core, for common fields like features, number of queues, ...
17 - virtio transport (pci, ccw, ...), for the different proxy devices and
20 - virtio device (net, blk, ...), for the different device types and their
34 virtio core virtio transport virtio device
62 - virtio-1 virtqueue
71 virtio core virtio transport virtio device
96 - virtio-1 virtqueue
/openbmc/linux/Documentation/translations/zh_TW/filesystems/
H A Dvirtiofs.rst17 virtiofs: virtio-fs 主機<->客機共享文件系統
24 Linux的virtiofs文件系統實現了一個半虛擬化VIRTIO類型「virtio-fs」設備的驅動，通過該\
31 步驟，且將存儲網絡暴露給客機。而virtio-fs設備通過提供不經過網絡的文件系統訪問文件\
45 請查閱 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守護程序的詳細信息。
49 由於virtio-fs設備將FUSE協議用於文件系統請求，因此Linux的virtiofs文件系統與FUSE文\
51 間之間的/dev/fuse接口由virtio-fs設備接口代替。
58 其關鍵，因爲此時不可能加入高優先級的請求。爲了解決此差異，virtio-fs設備採用「hiprio」\
/openbmc/qemu/docs/system/s390x/
H A Dcss.rst5 functionless) channel paths, and channel devices (virtio-ccw, 3270, and
20 does not enable MSS (any Linux version that supports virtio also enables MSS).
38 * a virtio-net device, cssid/ssid/devno automatically assigned::
40 -device virtio-net-ccw
49 * a virtio-rng device in subchannel set ``0``::
51 -device virtio-rng-ccw,devno=fe.0.0042
59 * a virtio-gpu device in subchannel set ``2``::
61 -device virtio-gpu-ccw,devno=fe.2.1111
69 * a virtio-mouse device in a non-standard channel subsystem image::
71 -device virtio-mouse-ccw,devno=2.0.2222
[all …]
/openbmc/qemu/docs/interop/
H A Dvhost-user.json21 # @9p: 9p virtio console
22 # @balloon: virtio balloon
23 # @block: virtio block
24 # @caif: virtio caif
25 # @console: virtio console
26 # @crypto: virtio crypto
27 # @gpu: virtio gpu
28 # @input: virtio input
29 # @net: virtio net
30 # @rng: virtio rng
[all …]
/openbmc/qemu/docs/system/
H A Dvirtio-net-failover.rst2 QEMU virtio-net standby (net_failover)
5 This document explains the setup and usage of virtio-net standby feature which
9 virtio-net device. Before migration the vfio device is unplugged and data flows
10 through the virtio-net device, on the target side another vfio-pci device is
15 networking device is called the primary device and the virtio-net device is the
30 networking device by falling back to a virtio-net device for the duration of
34 handler and traffic will go through the virtio-net device. On the target
43 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=52:54:00:6f:55:cc, \
50 failover_pair_id references the id of the virtio-net standby device. This
58 that if the virtio-net device is plugged first a warning will be issued that it
[all …]
/openbmc/linux/Documentation/virt/kvm/s390/
H A Ds390-diag.rst38 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 …]
/openbmc/openbmc/poky/meta/conf/machine/include/riscv/
H A Dqemuriscv.inc33 QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
34 QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device virtio-blk-device,drive=d…
35 QB_SERIAL_OPT = "-device virtio-serial-device -chardev null,id=virtcon -device virtconsole,chardev=…
36 QB_TCPSERIAL_OPT = " -device virtio-serial-device -chardev socket,id=virtcon,port=@PORT@,host=127.0…
39 QB_OPT_APPEND:riscv32 = "-device virtio-tablet-pci -device virtio-keyboard-pci"
/openbmc/openbmc/poky/meta/conf/machine/include/loongarch/
H A Dqemuloongarch.inc30 QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
31 QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device virtio-blk-device,drive=d…
32 QB_SERIAL_OPT = "-device virtio-serial-pci -chardev null,id=virtcon -device virtconsole,chardev=vir…
33 QB_TCPSERIAL_OPT = " -device virtio-serial-pci -chardev socket,id=virtcon,port=@PORT@,host=127.0.0.…
34 # Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
35 QB_OPT_APPEND = " -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rn…
/openbmc/qemu/qapi/
H A Dvirtio.json25 # @x-query-virtio:
64 { 'command': 'x-query-virtio',
117 # Full status of the virtio device with most VirtIODevice members.
192 # @x-query-virtio-status:
194 # Poll for a comprehensive status of a given virtio device
202 # Returns: VirtioStatus of the virtio device
209 # Poll for the status of virtio-crypto (no vhost-crypto active)
269 # Poll for the status of virtio-net (vhost-net is active)
438 { 'command': 'x-query-virtio-status',
446 # A structure defined to list the configuration statuses of a virtio
[all …]

12345678910>>...13