From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.oasis-open.org, mst@redhat.com,
david.edmondson@oracle.com
Cc: virtio-dev@lists.oasis-open.org, sburla@marvell.com,
jasowang@redhat.com, yishaih@nvidia.com, maorg@nvidia.com,
shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v10 4/4] transport-pci: Introduce group legacy group member config region access
Date: Thu, 06 Jul 2023 18:28:21 +0200 [thread overview]
Message-ID: <87r0pluhqy.fsf@redhat.com> (raw)
In-Reply-To: <20230706041714.65600-5-parav@nvidia.com>
On Thu, Jul 06 2023, Parav Pandit <parav@nvidia.com> wrote:
> diff --git a/transport-pci-legacy-regs.tex b/transport-pci-legacy-regs.tex
> new file mode 100644
> index 0000000..ceea28c
> --- /dev/null
> +++ b/transport-pci-legacy-regs.tex
> @@ -0,0 +1,42 @@
> +\subsection{Legacy Interface: Group member device Configuration Region Access}\label{sec:Virtio Transport Options / Virtio Over PCI Bus / Legacy Interface: Group Member Device Configuration Region Access}
> +
> +The PCI owner device or the member device or both support driver notifications using
What about
"The PCI owner device, the member device, or both can choose to
support..." ?
> +a notification region defined in \field{struct virtio_pci_legacy_notify_region}.
> +
> +In \field{struct virtio_virtio_admin_cmd_legacy_notify_query_entry},
> +\field{region_data} is defined as following:
> +
> +\begin{lstlisting}
> +struct virtio_pci_legacy_notify_region {
> + u8 owner; /* When set to 1, notification region is of the owner device */
> + u8 bar; /* BAR of the member or owner device */
> + u8 padding[6];
> + le64 offset; /* Offset within bar. */
> +};
> +\end{lstlisting}
> +
> +The group owner device hardwires VF BAR0 to zero in the SR-IOV Extended
> +capability.
> +
> +The group member device does not use PCI BAR0 in all the Virtio PCI capabilities
"in [or for?] any of the...", I guess?
> +listed in section \ref{sec:Virtio Transport Options / Virtio Over PCI Bus / Virtio Structure PCI Capabilities}.
> +
> +\devicenormative{\subsubsection}{Legacy Interface: Group Member Device Legacy Configuration Region Access}{Virtio Transport Options / Virtio Over PCI Bus / Legacy Interface: Group Member Device Configuration Region Access}
> +
> +When a PCI SR-IOV group owner device supports
> +VIRTIO_ADMIN_CMD_LEGACY_COMMON_CFG_READ,
> +VIRTIO_ADMIN_CMD_LEGACY_COMMON_CFG_WRITE, VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_READ,
> +VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_WRITE commands, the group owner device MUST
> +hardwire VF BAR0 to zero in the SR-IOV Extended capability and the group memberi
s/memberi/member/
> +device MUST NOT use BAR0 in any of the Virtio Structure PCI Capabilities.
> +
> +The group owner device or the group member device or both MAY support driver
> +notifications region.
Make this "a driver notification region"?
> +
> +For the SR-IOV group type, the owner device supporting
> +VIRTIO_ADMIN_CMD_LEGACY_COMMON_CFG_READ,
> +VIRTIO_ADMIN_CMD_LEGACY_COMMON_CFG_WRITE, VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_READ,
> +VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_WRITE and VIRTIO_ADMIN_CMD_LEGACY_NOTIFY_QUERY
> +commands and its member device SHOULD follow the rules for the PCI Device ID,
> +Revision ID and Subsystem Device ID of the non-transitional devices documented in
> +section \ref{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Discovery}.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-07-06 16:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 4:17 [virtio-dev] [PATCH v10 0/4] admin: Access legacy registers using admin commands Parav Pandit
2023-07-06 4:17 ` [virtio-dev] [PATCH v10 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-07-06 4:17 ` [virtio-dev] [PATCH v10 2/4] admin: Fix section numbering Parav Pandit
2023-07-06 13:39 ` [virtio-dev] " Cornelia Huck
2023-07-06 4:17 ` [virtio-dev] [PATCH v10 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-07-06 16:12 ` [virtio-dev] " Cornelia Huck
2023-07-06 16:16 ` [virtio-dev] " Parav Pandit
2023-07-06 4:17 ` [virtio-dev] [PATCH v10 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-07-06 16:28 ` Cornelia Huck [this message]
2023-07-06 16:33 ` [virtio-dev] " Parav Pandit
2023-07-06 16:42 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 16:58 ` [virtio-dev] " Parav Pandit
2023-07-06 17:33 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 17:47 ` [virtio-dev] " Parav Pandit
2023-07-06 18:06 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 18:16 ` [virtio-dev] " Parav Pandit
2023-07-06 18:48 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 18:53 ` [virtio-dev] " Parav Pandit
2023-07-06 18:56 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 19:00 ` [virtio-dev] " Parav Pandit
2023-07-06 19:42 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 20:21 ` [virtio-dev] " Parav Pandit
2023-07-06 20:28 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 20:35 ` [virtio-dev] " Parav Pandit
2023-07-06 20:41 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 20:43 ` [virtio-dev] " Parav Pandit
2023-07-07 8:12 ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
2023-07-07 8:32 ` Michael S. Tsirkin
2023-07-06 17:38 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 16:47 ` [virtio-dev] " Cornelia Huck
2023-07-06 16:52 ` Parav Pandit
2023-07-06 16:39 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 16:45 ` [virtio-dev] " Parav Pandit
2023-07-06 16:50 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 16:54 ` [virtio-dev] " Parav Pandit
2023-07-06 19:00 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 19:07 ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
2023-07-06 19:59 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 20:28 ` [virtio-dev] " Parav Pandit
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=87r0pluhqy.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=jasowang@redhat.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=yishaih@nvidia.com \
/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