From: "Michael S. Tsirkin" <mst@redhat.com>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: brett.creeley@amd.com, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, eperezma@redhat.com,
simon.horman@corigine.com, kuba@kernel.org, drivers@pensando.io,
davem@davemloft.net
Subject: Re: [PATCH net-next] virtio: kdoc for struct virtio_pci_modern_device
Date: Tue, 12 Sep 2023 16:53:43 -0400 [thread overview]
Message-ID: <20230912165335-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230911213104.14391-1-shannon.nelson@amd.com>
On Mon, Sep 11, 2023 at 02:31:04PM -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@corigine.com/
> Cc: Simon Horman <simon.horman@corigine.com>
> Signed-off-by: Shannon Nelson <shannon.nelson@amd.com>
> Acked-by: Eugenio Pérez <eperezma@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> include/linux/virtio_pci_modern.h | 34 ++++++++++++++++++++-----------
> 1 file changed, 22 insertions(+), 12 deletions(-)
>
> diff --git a/include/linux/virtio_pci_modern.h b/include/linux/virtio_pci_modern.h
> index 067ac1d789bc..a38c729d1973 100644
> --- a/include/linux/virtio_pci_modern.h
> +++ b/include/linux/virtio_pci_modern.h
> @@ -12,37 +12,47 @@ struct virtio_pci_modern_common_cfg {
> __le16 queue_reset; /* read-write */
> };
>
> +/**
> + * struct virtio_pci_modern_device - info for modern PCI virtio
> + * @pci_dev: Ptr to the PCI device struct
> + * @common: Position of the common capability in the PCI config
> + * @device: Device-specific data (non-legacy mode)
> + * @notify_base: Base of vq notifications (non-legacy mode)
> + * @notify_pa: Physical base of vq notifications
> + * @isr: Where to read and clear interrupt
> + * @notify_len: So we can sanity-check accesses
> + * @device_len: So we can sanity-check accesses
> + * @notify_map_cap: Capability for when we need to map notifications per-vq
> + * @notify_offset_multiplier: Multiply queue_notify_off by this value
> + * (non-legacy mode).
> + * @modern_bars: Bitmask of BARs
> + * @id: Device and vendor id
> + * @device_id_check: Callback defined before vp_modern_probe() to be used to
> + * verify the PCI device is a vendor's expected device rather
> + * than the standard virtio PCI device
> + * Returns the found device id or ERRNO
> + * @dma_mask: Optional mask instead of the traditional DMA_BIT_MASK(64),
> + * for vendor devices with DMA space address limitations
> + */
> struct virtio_pci_modern_device {
> struct pci_dev *pci_dev;
>
> struct virtio_pci_common_cfg __iomem *common;
> - /* Device-specific data (non-legacy mode) */
> void __iomem *device;
> - /* Base of vq notifications (non-legacy mode). */
> void __iomem *notify_base;
> - /* Physical base of vq notifications */
> resource_size_t notify_pa;
> - /* Where to read and clear interrupt */
> u8 __iomem *isr;
>
> - /* So we can sanity-check accesses. */
> size_t notify_len;
> size_t device_len;
>
> - /* Capability for when we need to map notifications per-vq. */
> int notify_map_cap;
>
> - /* Multiply queue_notify_off by this value. (non-legacy mode). */
> u32 notify_offset_multiplier;
> -
> int modern_bars;
> -
> struct virtio_device_id id;
>
> - /* optional check for vendor virtio device, returns dev_id or -ERRNO */
> int (*device_id_check)(struct pci_dev *pdev);
> -
> - /* optional mask for devices with limited DMA space */
> u64 dma_mask;
> };
>
> --
> 2.17.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-09-12 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 21:31 [PATCH net-next] virtio: kdoc for struct virtio_pci_modern_device Shannon Nelson via Virtualization
2023-09-12 4:20 ` Jason Wang
2023-09-12 20:53 ` Michael S. Tsirkin [this message]
2023-09-12 20:54 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230912165335-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=eperezma@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.com \
--cc=simon.horman@corigine.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).