Home
last modified time | relevance | path

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

/linux-4.4.14/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-4.4.14/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 …]
Dapi.txt1613 For the special case of virtio-ccw devices on s390, the ioevent is matched
1627 For virtio-ccw devices, addr contains the subchannel id and datamatch the
2401 KVM_S390_INT_VIRTIO (vm) - virtio external interrupt; external interrupt
/linux-4.4.14/drivers/virtio/
DKconfig4 This option is selected by any driver which implements the virtio
11 tristate "PCI driver for virtio devices"
15 This driver provides support for virtio based paravirtual device
17 virtio backends. Most QEMU based VMMs should support these devices
23 bool "Support for legacy virtio draft 0.9.X and older devices"
35 so, you can happily disable this option and virtio will not
56 This driver supports virtio input devices such as
62 tristate "Platform bus driver for memory mapped virtio devices"
66 This drivers provides support for memory mapped virtio
72 bool "Memory mapped virtio devices parameter parsing"
[all …]
DMakefile1 obj-$(CONFIG_VIRTIO) += virtio.o virtio_ring.o
Dvirtio_input.c384 MODULE_DEVICE_TABLE(virtio, id_table);
Dvirtio_balloon.c620 MODULE_DEVICE_TABLE(virtio, id_table);
/linux-4.4.14/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-4.4.14/drivers/vhost/
DKconfig2 tristate "Host kernel accelerator for virtio net"
22 for use with virtio-scsi guests
28 the host side of a virtio ring.
41 ordering from host while using legacy virtio.
/linux-4.4.14/Documentation/
Dremoteproc.txt17 duplicated. In addition, this framework also adds rpmsg virtio devices
21 (for more information about the virtio-based rpmsg bus and its drivers,
23 Registration of other types of virtio devices is now also possible. Firmwares
24 just need to publish what kind of virtio devices do they support, and then
26 existing virtio drivers with remote processor backends at a minimal development
120 context, which will look for virtio devices supported by the rproc's
122 If found, those virtio devices will be created and added, so as a result
123 of registering this remote processor, additional virtio drivers might get
163 handlers. If rpmsg/virtio functionality is also desired, then the ->kick handler
208 supported virtio devices (and their configurations).
[all …]
Drpmsg.txt32 Rpmsg is a virtio-based messaging bus that allows kernel drivers to communicate
72 a tx buffer and puts it back on virtio's used descriptor ring),
89 a tx buffer and puts it back on virtio's used descriptor ring),
107 a tx buffer and puts it back on virtio's used descriptor ring),
279 virtio device feature set. This feature bit means that the remote
292 The plan is also to add static creation of rpmsg channels via the virtio
Dkernel-parameters.txt124 VMMIO Driver for memory mapped virtio devices is enabled.
4007 [VMMIO] Memory mapped virtio (platform) device.
Ddevices.txt455 238 = /dev/vhost-net Host kernel accelerator for virtio net
/linux-4.4.14/drivers/gpu/drm/virtio/
DMakefile7 virtio-gpu-y := virtgpu_drv.o virtgpu_kms.o virtgpu_drm_bus.o virtgpu_gem.o \
12 obj-$(CONFIG_DRM_VIRTIO_GPU) += virtio-gpu.o
DKconfig11 This is the virtual GPU driver for virtio. It can be used with
Dvirtgpu_drv.c98 MODULE_DEVICE_TABLE(virtio, id_table);
/linux-4.4.14/Documentation/mic/
Dmic_overview.txt17 the standard virtio framework for network, disk and console devices,
18 though in our case the virtio framework is used across a PCIe bus.
25 and used only by the host driver to transfer data for the virtio devices.
36 virtio backends are situated on the host rather than the card given better
39 the fact that the virtio block storage backend can only be on the host.
/linux-4.4.14/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-4.4.14/drivers/s390/
DMakefile5 obj-y += cio/ block/ char/ crypto/ net/ scsi/ virtio/
/linux-4.4.14/tools/
DMakefile55 cgroup firewire hv guest usb virtio vm net iio: FORCE target
86 virtio vm net x86_energy_perf_policy \
/linux-4.4.14/tools/virtio/
DMakefile7 vpath %.c ../../drivers/virtio ../../drivers/vhost
/linux-4.4.14/arch/x86/lguest/
DKconfig13 If you say Y here, make sure you say Y (or M) to the virtio block
/linux-4.4.14/drivers/char/hw_random/
DMakefile20 obj-$(CONFIG_HW_RANDOM_VIRTIO) += virtio-rng.o
Dvirtio-rng.c210 MODULE_DEVICE_TABLE(virtio, id_table);
DKconfig230 module will be called virtio-rng. If unsure, say N.
/linux-4.4.14/arch/s390/include/uapi/asm/
DKbuild50 header-y += virtio-ccw.h
/linux-4.4.14/drivers/net/caif/
DKconfig45 tristate "CAIF virtio transport driver"
Dcaif_virtio.c789 MODULE_DEVICE_TABLE(virtio, id_table);
/linux-4.4.14/drivers/gpu/drm/
DMakefile69 obj-$(CONFIG_DRM_VIRTIO_GPU) += virtio/
DKconfig250 source "drivers/gpu/drm/virtio/Kconfig"
/linux-4.4.14/arch/mips/pci/
DMakefile25 obj-$(CONFIG_MIPS_PCI_VIRTIO) += pci-virtio-guest.o
/linux-4.4.14/drivers/
DMakefile39 obj-$(CONFIG_VIRTIO) += virtio/
DKconfig129 source "drivers/virtio/Kconfig"
/linux-4.4.14/arch/arm64/boot/dts/arm/
Dfoundation-v8.dts234 compatible = "virtio,mmio";
Drtsm_ve-motherboard.dtsi223 compatible = "virtio,mmio";
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dhost-generic-pci.txt4 virtio-pci implementations found in kvmtool and other para-virtualised
/linux-4.4.14/drivers/net/
DKconfig267 big-endian legacy virtio device.
273 machine with a legacy virtio NIC, you should say N.
286 This is the virtual network driver for virtio. It can be used with
Dvirtio_net.c2044 MODULE_DEVICE_TABLE(virtio, id_table);
/linux-4.4.14/drivers/misc/mic/
DKconfig65 virtio devices. Intel MIC X100 devices are currently supported.
/linux-4.4.14/net/9p/
Dtrans_virtio.c774 MODULE_DEVICE_TABLE(virtio, id_table);
/linux-4.4.14/Documentation/devicetree/bindings/
Dvendor-prefixes.txt240 virtio Virtual I/O Device Specification, developed by the OASIS consortium
/linux-4.4.14/drivers/rpmsg/
Dvirtio_rpmsg_bus.c1143 MODULE_DEVICE_TABLE(virtio, id_table);
/linux-4.4.14/arch/s390/
DKconfig865 prompt "s390 support for virtio devices"
871 Enabling this option adds support for virtio based paravirtual device
/linux-4.4.14/drivers/block/
Dvirtio_blk.c899 MODULE_DEVICE_TABLE(virtio, id_table);
DKconfig508 This is the virtual block driver for virtio. It can be used with
/linux-4.4.14/drivers/scsi/
Dvirtio_scsi.c1166 MODULE_DEVICE_TABLE(virtio, id_table);
DKconfig1756 tristate "virtio-scsi support"
1759 This is the virtual HBA driver for virtio. If the kernel will
/linux-4.4.14/drivers/char/
Dvirtio_console.c2318 MODULE_DEVICE_TABLE(virtio, id_table);
/linux-4.4.14/Documentation/arm64/
Darm-acpi.txt419 { .compatible = "virtio,mmio", },
/linux-4.4.14/
DMAINTAINERS11403 F: drivers/virtio/
11404 F: tools/virtio/
11417 F: drivers/s390/virtio/
11425 F: drivers/gpu/drm/virtio/
11440 F: drivers/virtio/virtio_input.c