search for: virtio_pci_modern_device

Displaying 6 results from an estimated 6 matches for "virtio_pci_modern_device".

2023 Aug 28
1
[PATCH net] virtio: kdoc for struct virtio_pci_modern_device
Finally following up to Simon's suggestion for some kdoc attention on struct virtio_pci_modern_device. Link: https://lore.kernel.org/netdev/ZE%2FQS0lnUvxFacjf at corigine.com/ Cc: Simon Horman <simon.horman at corigine.com> Signed-off-by: Shannon Nelson <shannon.nelson at amd.com> --- include/linux/virtio_pci_modern.h | 34 ++++++++++++++++++++----------- 1 file changed, 22 insertions...
2023 Aug 31
1
[PATCH net] virtio: kdoc for struct virtio_pci_modern_device
Hi, On Mon, 2023-08-28 at 14:34 -0700, Shannon Nelson wrote: > Finally following up to Simon's suggestion for some kdoc attention > on struct virtio_pci_modern_device. > > Link: https://lore.kernel.org/netdev/ZE%2FQS0lnUvxFacjf at corigine.com/ > Cc: Simon Horman <simon.horman at corigine.com> > Signed-off-by: Shannon Nelson <shannon.nelson at amd.com> IMHO this is net-next material and net-next is closed, so please repost this with a p...
2023 May 03
1
[PATCH v5 virtio 02/11] virtio: allow caller to override device DMA mask in vp_modern
To add a bit of vendor flexibility with various virtio based devices, allow the caller to specify a different DMA mask. This adds a dma_mask field to struct virtio_pci_modern_device. If defined by the driver, this mask will be used in a call to dma_set_mask_and_coherent() instead of the traditional DMA_BIT_MASK(64). This allows limiting the DMA space on vendor devices with address limitations. Signed-off-by: Shannon Nelson <shannon.nelson at amd.com> --- drivers/virt...
2023 May 03
1
[PATCH v5 virtio 01/11] virtio: allow caller to override device id in vp_modern
To add a bit of vendor flexibility with various virtio based devices, allow the caller to check for a different device id. This adds a function pointer field to struct virtio_pci_modern_device to specify an override device id check. If defined by the driver, this function will be called to check that the PCI device is the vendor's expected device, and will return the found device id to be stored in mdev->id.device. This allows vendors with alternative vendor device ids to use th...
2023 Mar 23
0
[PATCH v3 virtio 1/8] virtio: allow caller to override device id and DMA mask
...t; > diff --git a/drivers/virtio/virtio_pci_modern_dev.c b/drivers/virtio/virtio_pci_modern_dev.c > index 869cb46bef96..6ad1bb9ae8fa 100644 > --- a/drivers/virtio/virtio_pci_modern_dev.c > +++ b/drivers/virtio/virtio_pci_modern_dev.c > @@ -221,18 +221,25 @@ int vp_modern_probe(struct virtio_pci_modern_device *mdev) > > check_offsets(); > > - /* We only own devices >= 0x1000 and <= 0x107f: leave the rest. */ > - if (pci_dev->device < 0x1000 || pci_dev->device > 0x107f) > - return -ENODEV; > - > - if (pci_dev->device &lt...
2023 Mar 17
0
[PATCH RFC v2 virtio 3/7] pds_vdpa: virtio bar setup for vdpa
...aybe a function pointer to something that can validate the device id, > and a bitmask for setting DMA mapping; if they are 0/NULL, use the > default device id check and DMA mask. > > Adding them as extra arguments to the function call seems a bit messy, > maybe add them to the struct virtio_pci_modern_device and the caller can > set them as overrides if needed? > > struct virtio_pci_modern_device { > > ... > > int (*device_id_check_override(struct pci_dev *pdev)); > u64 dma_mask_override; > } Looks fine. Thanks