Home
last modified time | relevance | path

Searched full:virtqueues (Results 1 – 25 of 52) sorted by relevance

123

/linux-6.8/Documentation/driver-api/virtio/
Dvirtio.rst24 Device - Driver communication: virtqueues
37 virtqueues, which are actually ring buffers [#f1]_ of buffer descriptors
46 Refer to Chapter 2.5 ("Virtqueues") of the virtio spec (`[1]`_) for the
47 reference definitions of virtqueues and "Virtqueues and virtio ring: How
126 At this point, the virtqueues will be allocated and configured by
140 _`[2]` Virtqueues and virtio ring: How the data travels
141 https://www.redhat.com/en/blog/virtqueues-and-virtio-ring-how-data-travels
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 */
124 ("DRIVER_OK"). The virtqueues are anyway enabled automatically by the
130 In any case, the virtqueues need to be enabled before adding buffers to
/linux-6.8/drivers/virtio/
Dvirtio_pci_common.h38 /* the list node for the virtqueues list */
71 struct list_head virtqueues; member
73 /* Array of all virtqueues reported in the
110 * virtqueues Thus, we need at least 2 vectors for MSI. */
Dvirtio_vdpa.c35 struct list_head virtqueues; member
42 /* the list node for the virtqueues list */
252 list_add(&info->node, &vd_dev->virtqueues); in virtio_vdpa_setup_vq()
503 INIT_LIST_HEAD(&vd_dev->virtqueues); in virtio_vdpa_probe()
Dvirtio_pci_common.c58 /* Notify all virtqueues on an interrupt. */
67 list_for_each_entry(info, &vp_dev->virtqueues, node) { in vp_vring_interrupt()
161 "%s-virtqueues", name); in vp_request_msix_vectors()
197 list_add(&info->node, &vp_dev->virtqueues); in vp_setup_vq()
570 INIT_LIST_HEAD(&vp_dev->virtqueues); in virtio_pci_probe()
Dvirtio_mmio.c94 struct list_head virtqueues; member
101 /* the list node for the virtqueues list */
299 /* Notify all virtqueues on an interrupt. */
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-6.8/Documentation/filesystems/
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
71 prioritize certain requests over others. Virtqueues have queue semantics and
/linux-6.8/include/uapi/linux/
Dvhost.h48 /* By default, a device gets one vhost_worker that its virtqueues share. This
50 * for the device. It can later be bound to 1 or more of its virtqueues using
93 * virtqueues.
96 * is no longer attached to any virtqueues, it can be freed with
182 /* Get the count of all virtqueues */
Dvirtio_scmi.h18 /* Virtqueues */
Dvirtio_net.h299 * the device, the device will not steer new packets on receive virtqueues
300 * other than specified nor read from transmit virtqueues other than specified.
301 * Accordingly, driver should not transmit new packets on virtqueues other than
Dvduse.h28 * @vq_num: the number of virtqueues
132 * Setup the specified virtqueue. Make sure all virtqueues have been
Dvirtio_config.h119 * This feature indicates that the device support administration virtqueues.
Dvhost_types.h184 /* Device supports the driver enabling virtqueues both before and after
/linux-6.8/tools/include/uapi/linux/
Dvhost.h48 /* By default, a device gets one vhost_worker that its virtqueues share. This
50 * for the device. It can later be bound to 1 or more of its virtqueues using
93 * virtqueues.
96 * is no longer attached to any virtqueues, it can be freed with
182 /* Get the count of all virtqueues */
/linux-6.8/Documentation/userspace-api/
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-6.8/include/linux/
Dvirtio.h16 * @list: the chain of virtqueues for this device
126 * @vqs: the list of virtqueues for this device.
Dvirtio_config.h52 * @find_vqs: find virtqueues and instantiate them.
54 * nvqs: the number of virtqueues to find
55 * vqs: on success, includes new virtqueues
61 * @del_vqs: free virtqueues found by find_vqs().
/linux-6.8/sound/virtio/
Dvirtio_card.c99 * virtsnd_find_vqs() - Enumerate and initialize all virtqueues.
130 dev_err(&vdev->dev, "failed to initialize virtqueues\n"); in virtsnd_find_vqs()
/linux-6.8/drivers/vdpa/ifcvf/
Difcvf_base.c83 * all virtqueues. It is the minimal size that can be
84 * suppprted by all virtqueues.
/linux-6.8/drivers/crypto/virtio/
Dvirtio_crypto_common.h80 /* Does the affinity hint is set for virtqueues? */
/linux-6.8/drivers/scsi/
Dvirtio_scsi.c43 "The number of dedicated virtqueues for polling I/O");
633 * virtqueues once. in virtscsi_tmf()
833 /* Stop all the virtqueues. */ in virtscsi_remove_vqs()
886 /* Discover virtqueues and write information to configuration. */ in virtscsi_init()
/linux-6.8/drivers/block/
Dvirtio_blk.c43 MODULE_PARM_DESC(poll_queues, "The number of dedicated virtqueues for polling I/O");
1030 /* Discover virtqueues and write information to configuration. */ in init_vq()
1577 /* Stop all the virtqueues. */ in virtblk_remove()
1580 /* Virtqueues are stopped, nothing can use vblk->vdev anymore. */ in virtblk_remove()
1596 /* Ensure no requests in virtqueues before deleting vqs. */ in virtblk_freeze()
/linux-6.8/drivers/s390/virtio/
Dvirtio_ccw.c68 struct list_head virtqueues; member
304 list_for_each_entry(info, &vcdev->virtqueues, node) in virtio_ccw_drop_indicators()
586 list_add(&info->node, &vcdev->virtqueues); in virtio_ccw_setup_vq()
1087 list_for_each_entry(info, &vcdev->virtqueues, node) { in virtio_ccw_vq_by_ind()
1347 INIT_LIST_HEAD(&vcdev->virtqueues); in virtio_ccw_online()
/linux-6.8/Documentation/devicetree/bindings/remoteproc/
Dst,stm32-rproc.yaml68 A channel (a) used to communicate through virtqueues with the
/linux-6.8/drivers/firmware/arm_scmi/
Dvirtio.c600 * dequeued from the virtqueues (VIO_MSG_POLL_DONE): this is needed since such
649 * this means that it is possible to poll the virtqueues waiting for something
663 * in virtqueues handling mechanisms), we similarly kick the deferred worker

123