Home
last modified time | relevance | path

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

1234

/Linux-v5.10/tools/virtio/virtio-trace/
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 …]
/Linux-v5.10/Documentation/devicetree/bindings/virtio/
Dmmio.txt1 * 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";
Diommu.txt1 * 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";
/Linux-v5.10/drivers/virtio/
DKconfig5 This option is selected by any driver which implements the virtio
22 tristate "PCI driver for virtio devices"
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"
46 so, you can happily disable this option and virtio will not
53 tristate "vDPA driver for virtio devices"
57 This driver provides support for virtio based paravirtual
60 physical device to allow the datapath of virtio to be
66 tristate "Support for virtio pmem driver"
[all …]
DMakefile2 obj-$(CONFIG_VIRTIO) += virtio.o virtio_ring.o
/Linux-v5.10/arch/arc/boot/dts/
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";
/Linux-v5.10/Documentation/translations/zh_CN/filesystems/
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”\
/Linux-v5.10/Documentation/virt/kvm/
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 …]
/Linux-v5.10/arch/arm64/boot/dts/arm/
Drtsm_ve-motherboard-rs2.dtsi13 virtio-p9@140000 {
14 compatible = "virtio,mmio";
19 virtio-net@150000 {
20 compatible = "virtio,mmio";
/Linux-v5.10/drivers/vhost/
DKconfig14 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-v5.10/Documentation/filesystems/
Dvirtiofs.rst6 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
D9p.rst47 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.
68 virtio connect to the next virtio channel available
/Linux-v5.10/Documentation/staging/
Dremoteproc.rst20 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 …]
/Linux-v5.10/drivers/gpu/drm/virtio/
DMakefile6 virtio-gpu-y := virtgpu_drv.o virtgpu_kms.o virtgpu_gem.o \
11 obj-$(CONFIG_DRM_VIRTIO_GPU) += virtio-gpu.o
DKconfig9 This is the virtual GPU driver for virtio. It can be used with
Dvirtgpu_trace.h51 #define TRACE_INCLUDE_PATH ../../drivers/gpu/drm/virtio
/Linux-v5.10/Documentation/networking/
Dnet_failover.rst28 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'/>
76 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
/Linux-v5.10/drivers/vdpa/
DKconfig6 datapath which complies with virtio specifications with
29 virtio dataplane traffic to hardware.
48 of virtio net datapath such that descriptors put on the ring will
/Linux-v5.10/net/vmw_vsock/
DKconfig54 tristate "virtio transport for Virtual Sockets"
58 This module implements a virtio transport for Virtual Sockets.
61 Sockets over virtio.
/Linux-v5.10/Documentation/virt/
Dne_overview.rst55 using virtio-vsock [5]. The primary VM has virtio-pci vsock emulated device,
56 while the enclave VM has a virtio-mmio vsock emulated device. The vsock device
58 APIC and IOAPIC - to get interrupts from virtio-vsock device. The virtio-mmio
/Linux-v5.10/drivers/s390/
DMakefile6 obj-y += cio/ block/ char/ crypto/ net/ scsi/ virtio/
/Linux-v5.10/tools/virtio/ringtest/
DREADME1 Partial implementation of various ring layouts, useful to tune virtio design.
/Linux-v5.10/drivers/crypto/virtio/
DKconfig9 This driver provides support for virtio crypto device. If you
/Linux-v5.10/tools/
DMakefile67 cgroup firewire hv guest bootconfig spi usb virtio vm bpf iio gpio objtool leds wmi pci firmware de… target
104 virtio vm bpf x86_energy_perf_policy \
/Linux-v5.10/tools/virtio/
DMakefile8 vpath %.c ../../drivers/virtio ../../drivers/vhost

1234