Home
last modified time | relevance | path

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

123456

/linux/drivers/virtio/
A D.built-in.a.cmd1 …virtio/built-in.a := echo >/dev/null; rm -f drivers/virtio/built-in.a; /usr/bin/ccache /home/test/…
A DKconfig5 This option is selected by any driver which implements the virtio
39 tristate "PCI driver for virtio devices"
72 tristate "vDPA driver for virtio devices"
76 This driver provides support for virtio based paravirtual
79 physical device to allow the datapath of virtio to be
85 tristate "Support for virtio pmem driver"
91 - with a virtio-based flushing interface.
129 This driver supports virtio input devices such as
139 This drivers provides support for memory mapped virtio
145 bool "Memory mapped virtio devices parameter parsing"
[all …]
A D.virtio.o.cmd1 …virtio/virtio.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/aarch6…
3 source_drivers/virtio/virtio.o := drivers/virtio/virtio.c
5 deps_drivers/virtio/virtio.o := \
23 include/linux/virtio.h \
1033 drivers/virtio/virtio.o: $(deps_drivers/virtio/virtio.o)
1035 $(deps_drivers/virtio/virtio.o):
/linux/tools/virtio/virtio-trace/
A DREADME1 Trace Agent for virtio-trace
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/
53 2) Set up of virtio-serial pipe in a host
54 Add qemu option to use virtio-serial pipe.
56 ##virtio-serial device##
57 -device virtio-serial-pci,id=virtio-serial0\
[all …]
/linux/Documentation/devicetree/bindings/virtio/
A Dvirtio-device.yaml4 $id: http://devicetree.org/schemas/virtio/virtio-device.yaml#
13 These bindings are applicable to virtio devices irrespective of the bus they
16 # We need a select here so we don't match all nodes with 'virtio,mmio'
19 pattern: "^virtio,device[0-9a-f]{1,8}$"
21 "virtio,deviceID", where ID is the virtio device id. The textual
32 virtio@3000 {
33 compatible = "virtio,mmio";
38 compatible = "virtio,device22";
A Dmmio.yaml4 $id: http://devicetree.org/schemas/virtio/mmio.yaml#
7 title: virtio memory mapped devices
13 See https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio for
18 const: virtio,mmio
27 description: Required when the node corresponds to a virtio-iommu device.
44 virtio@3000 {
45 compatible = "virtio,mmio";
54 compatible = "virtio,mmio";
A 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/Documentation/devicetree/bindings/i2c/
A Di2c-virtio.yaml4 $id: http://devicetree.org/schemas/i2c/i2c-virtio.yaml#
14 - $ref: /schemas/virtio/virtio-device.yaml#
17 Virtio I2C device, see /schemas/virtio/virtio-device.yaml for more details.
24 const: virtio,device22
33 virtio@3000 {
34 compatible = "virtio,mmio";
39 compatible = "virtio,device22";
/linux/Documentation/devicetree/bindings/gpio/
A Dgpio-virtio.yaml4 $id: http://devicetree.org/schemas/gpio/gpio-virtio.yaml#
13 - $ref: /schemas/virtio/virtio-device.yaml#
16 Virtio GPIO controller, see /schemas/virtio/virtio-device.yaml for more
24 const: virtio,device29
45 virtio@3000 {
46 compatible = "virtio,mmio";
51 compatible = "virtio,device29";
/linux/arch/arc/boot/dts/
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";
/linux/Documentation/translations/zh_CN/filesystems/
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”\
/linux/Documentation/translations/zh_TW/filesystems/
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」\
/linux/Documentation/virt/kvm/
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 …]
/linux/arch/arm64/boot/dts/arm/
A Drtsm_ve-motherboard-rs2.dtsi13 virtio-p9@140000 {
14 compatible = "virtio,mmio";
19 virtio-net@150000 {
20 compatible = "virtio,mmio";
/linux/drivers/vhost/
A 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/Documentation/filesystems/
A 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
A 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/Documentation/translations/zh_CN/virt/
A Dne_overview.rst57 enclave通过本地通信通道与主虚拟机进行通信，使用virtio-vsock[5]。主虚拟机有
58 virtio-pci vsock模拟设备，而飞地虚拟机有virtio-mmio vsock模拟设备。vsock
60 virtio-vsock设备获得中断。virtio-mmio设备被放置在典型的4 GiB以下的内存中。
/linux/Documentation/staging/
A 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,
27 just need to publish what kind of virtio devices do they support, and then
158 context, which will look for virtio devices supported by the rproc's
257 supported virtio devices (and their configurations).
315 * virtio header.
347 should specify the virtio device id (as in virtio_ids.h), virtio features,
348 virtio config space, vrings information, etc.
351 will look for its resource table and will register the virtio devices
352 it supports. A firmware may support any number of virtio devices, and
[all …]
/linux/sound/virtio/
A D.built-in.a.cmd1 …virtio/built-in.a := echo >/dev/null; rm -f sound/virtio/built-in.a; /usr/bin/ccache /home/test/wo…
A DKconfig2 # Sound card driver for virtio
10 This is the virtual sound driver for virtio. Say Y or M.
/linux/Documentation/userspace-api/
A Dvduse.rst5 vDPA (virtio data path acceleration) device is a device that uses a
6 datapath which complies with the virtio specifications with vendor
14 Note that only virtio block device is supported by VDUSE framework now,
100 such as device name (uniquely identify a VDUSE device), virtio features, virtio
145 the virtio spec: https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html
147 status bit if the device can not accept the negotiated virtio features
/linux/drivers/vdpa/
A DKconfig7 datapath which complies with virtio specifications with
51 virtio dataplane traffic to hardware.
70 of virtio net datapath such that descriptors put on the ring will
79 This kernel module bridges virtio PCI device to vDPA bus.
87 virtio 0.9.5 specification.
/linux/Documentation/networking/
A 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/drivers/gpu/drm/virtio/
A DMakefile6 virtio-gpu-y := virtgpu_drv.o virtgpu_kms.o virtgpu_gem.o virtgpu_vram.o \
11 obj-$(CONFIG_DRM_VIRTIO_GPU) += virtio-gpu.o

Completed in 34 milliseconds

123456