Home
last modified time | relevance | path

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

123

/Linux-v4.19/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-v4.19/Documentation/virtual/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-v4.19/drivers/virtio/
DKconfig4 This option is selected by any driver which implements the virtio
15 tristate "PCI driver for virtio devices"
19 This driver provides support for virtio based paravirtual device
21 virtio backends. Most QEMU based VMMs should support these devices
27 bool "Support for legacy virtio draft 0.9.X and older devices"
39 so, you can happily disable this option and virtio will not
60 This driver supports virtio input devices such as
66 tristate "Platform bus driver for memory mapped virtio devices"
70 This drivers provides support for memory mapped virtio
76 bool "Memory mapped virtio devices parameter parsing"
[all …]
DMakefile2 obj-$(CONFIG_VIRTIO) += virtio.o virtio_ring.o
/Linux-v4.19/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
14 compatible = "virtio,mmio";
/Linux-v4.19/Documentation/mic/
Dmic_overview.txt17 leverages the standard virtio framework for network, disk and console
18 devices, though in our case the virtio framework is used across a PCIe
20 backends or devices on the host which are used to probe virtio drivers
22 in the kernel is used to access virtio rings from the host. The card
23 VOP driver allows card virtio drivers to communicate with their user
25 can add, remove and configure virtio devices. A thin MIC specific
34 and used only by the host driver to transfer data for the virtio devices.
45 virtio backends are situated on the host rather than the card given better
48 the fact that the virtio block storage backend can only be on the host.
/Linux-v4.19/drivers/vhost/
DKconfig2 tristate "Host kernel accelerator for virtio net"
20 for use with virtio-scsi guests
23 tristate "vhost virtio-vsock driver"
31 virtio_transport.ko driver loaded to use the virtio-vsock device.
47 ordering from host while using legacy virtio.
DKconfig.vringh5 the host side of a virtio ring.
/Linux-v4.19/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 …]
Drpmsg.txt37 Rpmsg is a virtio-based messaging bus that allows kernel drivers to communicate
81 a tx buffer and puts it back on virtio's used descriptor ring),
104 a tx buffer and puts it back on virtio's used descriptor ring),
128 a tx buffer and puts it back on virtio's used descriptor ring),
327 virtio device feature set. This feature bit means that the remote
340 The plan is also to add static creation of rpmsg channels via the virtio
/Linux-v4.19/drivers/gpu/drm/virtio/
DMakefile6 virtio-gpu-y := virtgpu_drv.o virtgpu_kms.o virtgpu_drm_bus.o virtgpu_gem.o \
11 obj-$(CONFIG_DRM_VIRTIO_GPU) += virtio-gpu.o
DKconfig7 This is the virtual GPU driver for virtio. It can be used with
/Linux-v4.19/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-v4.19/Documentation/filesystems/
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-v4.19/drivers/gpu/drm/cirrus/
DKconfig18 - virtio (DRM_VIRTIO_GPU), qemu -vga virtio)
/Linux-v4.19/net/vmw_vsock/
DKconfig41 tristate "virtio transport for Virtual Sockets"
45 This module implements a virtio transport for Virtual Sockets.
48 Sockets over virtio.
/Linux-v4.19/drivers/s390/
DMakefile6 obj-y += cio/ block/ char/ crypto/ net/ scsi/ virtio/
/Linux-v4.19/tools/virtio/ringtest/
DREADME1 Partial implementation of various ring layouts, useful to tune virtio design.
/Linux-v4.19/drivers/crypto/virtio/
DKconfig9 This driver provides support for virtio crypto device. If you
/Linux-v4.19/tools/
DMakefile62 cgroup firewire hv guest spi usb virtio vm bpf iio gpio objtool leds wmi: FORCE target
96 virtio vm bpf x86_energy_perf_policy \
/Linux-v4.19/tools/virtio/
DMakefile8 vpath %.c ../../drivers/virtio ../../drivers/vhost
/Linux-v4.19/arch/arm64/boot/dts/arm/
Dfoundation-v8.dtsi222 virtio-block@130000 {
223 compatible = "virtio,mmio";
Drtsm_ve-motherboard.dtsi224 virtio-block@130000 {
225 compatible = "virtio,mmio";
/Linux-v4.19/drivers/misc/mic/
DKconfig85 virtio devices. Intel MIC X100 devices are currently supported.
141 devices. The VOP driver allows virtio drivers, e.g. net, console
142 and block drivers, on the card connect to user space virtio
/Linux-v4.19/drivers/char/hw_random/
DMakefile21 obj-$(CONFIG_HW_RANDOM_VIRTIO) += virtio-rng.o

123