Home
last modified time | relevance | path

Searched refs:virtqueues (Results 1 – 6 of 6) sorted by relevance

/linux/Documentation/driver-api/virtio/
H A Dvirtio.rst24 Device - Driver communication: virtqueues
37 virtqueues, which are actually ring buffers [#f1]_ of buffer descriptors
47 reference definitions of virtqueues and "Virtqueues and virtio ring: How
126 At this point, the virtqueues will be allocated and configured by
141 https://www.redhat.com/en/blog/virtqueues-and-virtio-ring-how-data-travels
H A Dwriting_virtio_drivers.rst22 and configure the virtqueues for the device according to its spec, the
23 configuration of the virtqueues in the driver side must match the
87 /* remove virtqueues */
123 ("DRIVER_OK"). The virtqueues are anyway enabled automatically by the
129 In any case, the virtqueues need to be enabled before adding buffers to
/linux/Documentation/filesystems/
H A Dvirtiofs.rst68 Mapping /dev/fuse to virtqueues requires solving differences in semantics
69 between /dev/fuse and virtqueues. Each time the /dev/fuse device is read, the
/linux/drivers/virtio/
H A Dvirtio_mmio.c94 struct list_head virtqueues; member
319 list_for_each_entry(info, &vm_dev->virtqueues, node) in vm_interrupt()
470 list_add(&info->node, &vm_dev->virtqueues); in vm_setup_vq()
630 INIT_LIST_HEAD(&vm_dev->virtqueues); in virtio_mmio_probe()
/linux/Documentation/userspace-api/
H A Dvduse.rst101 configuration space, the number of virtqueues and so on for this emulated device.
221 3. Setup the kick eventfd for the specified virtqueues with the VDUSE_VQ_SETUP_KICKFD
/linux/Documentation/staging/
H A Dremoteproc.rst228 too expensive) to go through the existing virtqueues and look for new buffers