Home
last modified time | relevance | path

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

1234

/Linux-v5.4/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.4/arch/arc/boot/dts/
Dhaps_hs.dts66 virtio0: virtio@f0100000 {
67 compatible = "virtio,mmio";
72 virtio1: virtio@f0102000 {
73 compatible = "virtio,mmio";
78 virtio2: virtio@f0104000 {
79 compatible = "virtio,mmio";
84 virtio3: virtio@f0106000 {
85 compatible = "virtio,mmio";
90 virtio4: virtio@f0108000 {
91 compatible = "virtio,mmio";
/Linux-v5.4/Documentation/devicetree/bindings/virtio/
Dmmio.txt1 * virtio memory mapped device
3 See http://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.4/drivers/virtio/
DKconfig5 This option is selected by any driver which implements the virtio
16 tristate "PCI driver for virtio devices"
20 This driver provides support for virtio based paravirtual device
22 virtio backends. Most QEMU based VMMs should support these devices
28 bool "Support for legacy virtio draft 0.9.X and older devices"
40 so, you can happily disable this option and virtio will not
47 tristate "Support for virtio pmem driver"
51 This driver provides access to virtio-pmem devices, storage devices
53 - with a virtio-based flushing interface.
72 This driver supports virtio input devices such as
[all …]
DMakefile2 obj-$(CONFIG_VIRTIO) += virtio.o virtio_ring.o
/Linux-v5.4/Documentation/virt/kvm/
Ds390-diag.txt35 DIAGNOSE function code 'X'500' - KVM virtio functions
38 If the function code specifies 0x500, various virtio-related functions
41 General register 1 contains the virtio subfunction code. Supported
42 virtio subfunctions depend on KVM's userspace. Generally, userspace
43 provides either s390-virtio (subcodes 0-2) or virtio-ccw (subcode 3).
49 Subcode 0 - s390-virtio notification and early console printk
52 Subcode 1 - s390-virtio reset
55 Subcode 2 - s390-virtio set status
58 Subcode 3 - virtio-ccw notification
62 the subchannel of the virtio-ccw proxy device to be notified.
[all …]
/Linux-v5.4/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.4/Documentation/filesystems/
Dvirtiofs.rst4 virtiofs: virtio-fs host<->guest shared file system
12 VIRTIO "virtio-fs" device for guest<->host file system sharing. It allows a
22 expose the storage network to the guest. The virtio-fs device was designed to
25 Furthermore the virtio-fs device takes advantage of the co-location of the
37 Please see https://virtio-fs.gitlab.io/ for details on how to configure QEMU
42 Since the virtio-fs device uses the FUSE protocol for file system requests, the
46 with the virtio-fs device interface.
59 the virtio-fs device uses a "hiprio" virtqueue specifically for requests that
D9p.txt42 For server running on QEMU host with virtio transport:
44 mount -t 9p -o trans=virtio <mount_tag> /mnt/9
47 mount points. Each 9P export is seen by the client as a virtio device with an
49 seen by reading /sys/bus/virtio/drivers/9pnet_virtio/virtio<n>/mount_tag files.
60 virtio - connect to the next virtio channel available
/Linux-v5.4/Documentation/mic/
Dmic_overview.rst21 leverages the standard virtio framework for network, disk and console
22 devices, though in our case the virtio framework is used across a PCIe
24 backends or devices on the host which are used to probe virtio drivers
26 in the kernel is used to access virtio rings from the host. The card
27 VOP driver allows card virtio drivers to communicate with their user
29 can add, remove and configure virtio devices. A thin MIC specific
38 and used only by the host driver to transfer data for the virtio devices.
49 virtio backends are situated on the host rather than the card given better
52 the fact that the virtio block storage backend can only be on the host::
/Linux-v5.4/drivers/vhost/
DKconfig3 tristate "Host kernel accelerator for virtio net"
21 for use with virtio-scsi guests
24 tristate "vhost virtio-vsock driver"
32 virtio_transport.ko driver loaded to use the virtio-vsock device.
48 ordering from host while using legacy virtio.
DKconfig.vringh6 the host side of a virtio ring.
/Linux-v5.4/Documentation/
Dremoteproc.txt20 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.4/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
DKconfig8 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.4/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.4/drivers/gpu/drm/cirrus/
DKconfig19 - virtio (DRM_VIRTIO_GPU), qemu -vga virtio)
/Linux-v5.4/net/vmw_vsock/
DKconfig42 tristate "virtio transport for Virtual Sockets"
46 This module implements a virtio transport for Virtual Sockets.
49 Sockets over virtio.
/Linux-v5.4/drivers/s390/
DMakefile6 obj-y += cio/ block/ char/ crypto/ net/ scsi/ virtio/
/Linux-v5.4/tools/virtio/ringtest/
DREADME1 Partial implementation of various ring layouts, useful to tune virtio design.
/Linux-v5.4/drivers/crypto/virtio/
DKconfig10 This driver provides support for virtio crypto device. If you
/Linux-v5.4/tools/
DMakefile66 cgroup firewire hv guest spi usb virtio vm bpf iio gpio objtool leds wmi pci firmware debugging: FO… target
100 virtio vm bpf x86_energy_perf_policy \
/Linux-v5.4/tools/virtio/
DMakefile8 vpath %.c ../../drivers/virtio ../../drivers/vhost

1234