public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Zhu, Lingshan" <lingshan.zhu@intel.com>
Cc: Parav Pandit <parav@nvidia.com>,
	virtio-dev@lists.oasis-open.org, pasic@linux.ibm.com,
	cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
	shahafs@nvidia.com, Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [virtio-dev] Re: [PATCH 1/2] transport-pci: Improve config msix vector description
Date: Wed, 19 Apr 2023 07:27:06 -0400	[thread overview]
Message-ID: <20230419072522-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <588b201f-8da7-dc6e-d66e-1489914ef051@intel.com>

On Wed, Apr 19, 2023 at 04:25:13PM +0800, Zhu, Lingshan wrote:
> 
> 
> On 4/19/2023 3:05 PM, Michael S. Tsirkin wrote:
> > On Tue, Apr 11, 2023 at 10:42:19PM +0300, Parav Pandit wrote:
> > > config_msix_vector is the register that holds the MSI-X vector number
> > > for receiving configuration change related interrupts.
> > > 
> > > It is not "for MSI-X".
> > > 
> > > Hence, replace the confusing text with appropriate one.
> > > 
> > > Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> > > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > > 
> > > ---
> > > changelog:
> > > v0->v1:
> > > - added 'here'
> > > - dropped 'receiving'
> > > ---
> > >   transport-pci.tex | 3 ++-
> > >   1 file changed, 2 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/transport-pci.tex b/transport-pci.tex
> > > index 42be072..cb9fadd 100644
> > > --- a/transport-pci.tex
> > > +++ b/transport-pci.tex
> > > @@ -343,7 +343,8 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
> > >           Driver Feature Bits selected by \field{driver_feature_select}.
> > >   \item[\field{config_msix_vector}]
> > > -        The driver sets the Configuration Vector for MSI-X.
> > > +        The driver writes an MSI-X vector number here for Configuration change
> > > +        interrupts.
> > Hmm I think it's "the vector", not an. And the order of words
> > is unusual. We also don't normally use "writes here". Would
> > 
> > 	Used by the driver to set the MSI-X vector number for Configuration change interrupts.
> > 
> > be equally acceptable?
> Is it better also explain what is a MSI-X vector number here? Like saying
> the offset in the table or the slot number?
> 
> Thanks,
> Zhu Lingshan

It does, in fact, refer to the MSI-X entry. Vector is in fact the
contents of the entry.  The mixup between vector and entry dates back to
PCI spec which has text like
	While more accurately termed “per-entry masking”, masking an MSI-X Table entry is still
	referred to as “vector masking” so similar descriptions can be used for both MSI and MSI-
	X.


> > 
> > 
> > >   \item[\field{num_queues}]
> > >           The device specifies the maximum number of virtqueues supported here.
> > > -- 
> > > 2.26.2
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
> > 


---------------------------------------------------------------------
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-04-19 11:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 19:42 [virtio-dev] [PATCH 0/2] transport-pci: msix register desc improve Parav Pandit
2023-04-11 19:42 ` [virtio-dev] [PATCH 1/2] transport-pci: Improve config msix vector description Parav Pandit
2023-04-19  7:05   ` [virtio-dev] " Michael S. Tsirkin
2023-04-19  7:09     ` Michael S. Tsirkin
2023-04-19  8:25     ` Zhu, Lingshan
2023-04-19 11:27       ` Michael S. Tsirkin [this message]
2023-04-19 19:02         ` Parav Pandit
2023-04-11 19:42 ` [virtio-dev] [PATCH 2/2] transport-pci: Improve queue msix vector register desc Parav Pandit
2023-04-19  7:08   ` [virtio-dev] " Michael S. Tsirkin
2023-04-19  7:08     ` Michael S. Tsirkin
2023-04-19  1:53 ` [virtio-dev] RE: [PATCH 0/2] transport-pci: msix register desc improve 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=20230419072522-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=lingshan.zhu@intel.com \
    --cc=mgurtovoy@nvidia.com \
    --cc=parav@nvidia.com \
    --cc=pasic@linux.ibm.com \
    --cc=shahafs@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.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