public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
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 v9 4/4] transport-pci: Introduce group legacy group member config region access
Date: Wed, 05 Jul 2023 12:29:26 +0200	[thread overview]
Message-ID: <87cz163b3t.fsf@redhat.com> (raw)
In-Reply-To: <20230704233724.22394-5-parav@nvidia.com>

On Wed, Jul 05 2023, Parav Pandit <parav@nvidia.com> wrote:

> diff --git a/admin-cmds-legacy-interface.tex b/admin-cmds-legacy-interface.tex
> index 09001d5..571b256 100644
> --- a/admin-cmds-legacy-interface.tex
> +++ b/admin-cmds-legacy-interface.tex
> @@ -150,7 +150,7 @@ \subsubsection{Legacy Interfaces}\label{sec:Basic Facilities of a Virtio Device
>  by the device.
>  
>  Refer to the specific transport section for the definition of the
> -\field{region_data}.
> +\field{region_data}. For PCI transport refer to section \ref{sec:Virtio Transport Options / Virtio Over PCI Bus / Legacy Interface: Group Member Device Configuration Region Access}.

"For the PCI transport, refer to..."

>  
>  This command is currently only defined for the PCI SR-IOV group type.
>  

(...)

> diff --git a/transport-pci-legacy-regs.tex b/transport-pci-legacy-regs.tex
> new file mode 100644
> index 0000000..e4f70c9
> --- /dev/null
> +++ b/transport-pci-legacy-regs.tex
> @@ -0,0 +1,41 @@
> +\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 supports driver notifications using

s/supports/support/

> +a notification region defined in the \field{struct virtio_pci_notify_region}.

s/in the/in/

> +
> +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 hardwire VF BAR0 in the SR-IOV Extended capability.

s/hardwire/hardwires/

> +
> +The group member device does not use PCI BAR0 in various Virtio PCI capabilities

"in the various" caps? Or "in some of the" caps?

> +listed in section \ref{sec:Virtio Transport Options / Virtio Over PCI Bus / Virtio Structure PCI Capabilities}.


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-07-05 10:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 23:37 [virtio-dev] [PATCH v9 0/4] admin: Access legacy registers using admin commands Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-07-05 10:05   ` [virtio-dev] " Cornelia Huck
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 2/4] admin: Fix section numbering Parav Pandit
2023-07-05 10:09   ` [virtio-dev] " Cornelia Huck
2023-07-05 16:29     ` Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-07-05 10:24   ` [virtio-dev] " Cornelia Huck
2023-07-05 16:34     ` [virtio-dev] " Parav Pandit
2023-07-06  5:43       ` [virtio-dev] " Michael S. Tsirkin
2023-07-05 11:04   ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-07-05 18:26     ` [virtio-dev] " Parav Pandit
2023-07-06  6:01       ` [virtio-dev] " Michael S. Tsirkin
2023-07-05 22:01     ` [virtio-dev] " Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-07-05 10:29   ` Cornelia Huck [this message]
2023-07-05 16:36     ` [virtio-dev] " Parav Pandit
2023-07-05 10:56   ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-07-05 11:09 ` [virtio-dev] Re: [virtio-comment] [PATCH v9 0/4] admin: Access legacy registers using admin commands Michael S. Tsirkin
2023-07-05 13:01   ` [virtio-dev] " Parav Pandit
2023-07-05 13:42     ` Cornelia Huck
2023-07-05 14:37       ` Parav Pandit
2023-07-06  4:20   ` Parav Pandit
2023-07-06  6:10     ` [virtio-dev] " 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=87cz163b3t.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