| /linux-5.10/Documentation/filesystems/ |
| D | virtiofs.rst | 68 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-5.10/drivers/virtio/ |
| D | virtio_pci_common.h | 35 /* the list node for the virtqueues list */
77 struct list_head virtqueues; member
111 * virtqueues Thus, we need at least 2 vectors for MSI. */
|
| D | virtio_vdpa.c | 34 struct list_head virtqueues; member
41 /* the list node for the virtqueues list */
200 list_add(&info->node, &vd_dev->virtqueues); in virtio_vdpa_setup_vq()
348 INIT_LIST_HEAD(&vd_dev->virtqueues); in virtio_vdpa_probe()
|
| D | virtio_pci_common.c | 58 /* 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()
527 INIT_LIST_HEAD(&vp_dev->virtqueues); in virtio_pci_probe()
|
| D | virtio_mmio.c | 92 struct list_head virtqueues; member
99 /* the list node for the virtqueues list */
282 /* Notify all virtqueues on an interrupt. */
302 list_for_each_entry(info, &vm_dev->virtqueues, node) in vm_interrupt()
438 list_add(&info->node, &vm_dev->virtqueues); in vm_setup_vq()
574 INIT_LIST_HEAD(&vm_dev->virtqueues); in virtio_mmio_probe()
|
| D | virtio_balloon.c | 362 * While most virtqueues communicate guest-initiated requests to the hypervisor,
|
| /linux-5.10/include/uapi/linux/ |
| D | virtio_net.h | 293 * the device, the device will not steer new packets on receive virtqueues
294 * other than specified nor read from transmit virtqueues other than specified.
295 * Accordingly, driver should not transmit new packets on virtqueues other than
|
| /linux-5.10/include/linux/ |
| D | virtio.h | 15 * @list: the chain of virtqueues for this device
103 * @vqs: the list of virtqueues for this device.
|
| D | virtio_config.h | 50 * @find_vqs: find virtqueues and instantiate them.
52 * nvqs: the number of virtqueues to find
53 * vqs: on success, includes new virtqueues
59 * @del_vqs: free virtqueues found by find_vqs().
|
| /linux-5.10/drivers/crypto/virtio/ |
| D | virtio_crypto_common.h | 78 /* Does the affinity hint is set for virtqueues? */
|
| D | virtio_crypto_core.c | 79 /* Allocate/initialize parameters for data virtqueues */ in virtcrypto_find_vqs()
|
| /linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| D | st,stm32-rproc.yaml | 58 A channel (a) used to communicate through virtqueues with the
|
| /linux-5.10/drivers/vdpa/ |
| D | vdpa.c | 64 * @nvqs: number of virtqueues supported by this device
|
| /linux-5.10/drivers/s390/virtio/ |
| D | virtio_ccw.c | 66 struct list_head virtqueues; member
302 list_for_each_entry(info, &vcdev->virtqueues, node) in virtio_ccw_drop_indicators()
587 list_add(&info->node, &vcdev->virtqueues); in virtio_ccw_setup_vq()
1057 list_for_each_entry(info, &vcdev->virtqueues, node) { in virtio_ccw_vq_by_ind()
1307 INIT_LIST_HEAD(&vcdev->virtqueues); in virtio_ccw_online()
|
| /linux-5.10/drivers/block/ |
| D | virtio_blk.c | 528 /* Discover virtqueues and write information to configuration. */ in init_vq()
920 /* Stop all the virtqueues. */ in virtblk_remove()
923 /* Virtqueues are stopped, nothing can use vblk->vdev anymore. */ in virtblk_remove()
|
| /linux-5.10/drivers/scsi/ |
| D | virtio_scsi.c | 622 * virtqueues once. in virtscsi_tmf()
782 /* Stop all the virtqueues. */ in virtscsi_remove_vqs()
818 /* Discover virtqueues and write information to configuration. */ in virtscsi_init()
|
| /linux-5.10/fs/fuse/ |
| D | virtio_fs.c | 55 unsigned int nvqs; /* number of virtqueues */
668 /* Initialize virtqueues */
702 /* Initialize the requests virtqueues */ in virtio_fs_setup_vqs()
729 /* Free virtqueues (device must already be reset) */
|
| /linux-5.10/drivers/remoteproc/ |
| D | remoteproc_virtio.c | 80 /* we're temporarily limited to two virtqueues per rvdev */ in rp_find_vq()
|
| D | keystone_remoteproc.c | 229 * the remote processor is expected to process both its Tx and Rx virtqueues.
|
| D | ti_k3_dsp_remoteproc.c | 149 * the remote processor is expected to process both its Tx and Rx virtqueues.
|
| /linux-5.10/Documentation/staging/ |
| D | remoteproc.rst | 227 too expensive) to go through the existing virtqueues and look for new buffers
|
| /linux-5.10/net/vmw_vsock/ |
| D | virtio_transport.c | 676 /* Delete virtqueues and flush outstanding callbacks if any */ in virtio_vsock_remove()
|
| /linux-5.10/drivers/char/ |
| D | virtio_console.c | 149 * A couple of virtqueues for the control channel: one for
160 /* Array of per-port IO virtqueues */
1239 * leave this as zero, virtqueues have implicit notifications. in init_port_console()
|
| /linux-5.10/drivers/iommu/ |
| D | virtio-iommu.c | 1117 /* Stop all virtqueues */ in viommu_remove()
|
| /linux-5.10/drivers/rpmsg/ |
| D | virtio_rpmsg_bus.c | 902 /* We expect two virtqueues, rx and tx (and in this order) */ in rpmsg_probe()
|