[virtio-dev] [PATCH 0/3] transport-pci: msix summary update

[virtio-dev] [PATCH 0/3] transport-pci: msix summary update

[Parav Pandit]

Summary for config_msix_vector and queue_msix_vector
registers have a confusing text of "for MSI-X".

Rewrite the register summary line.

Patch summary:
patch 1 removes empty line at the end of the file
patch 2 updates configuration vector summary
patch 3 updates queue vector summary

These are only editorial changes to rewrite the summary.
Hence it should not require a github issue.

Parav Pandit (3):
  transport-pci: Remove empty line at end of file
  transport-pci: Improve config msix vector description
  transport-pci: Improve queue msix vector register desc

 transport-pci.tex | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

-- 
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

[virtio-dev] [PATCH 1/3] transport-pci: Remove empty line at end of file

[Parav Pandit]

Remove empty line at end of file.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
 transport-pci.tex | 1 -
 1 file changed, 1 deletion(-)

diff --git a/transport-pci.tex b/transport-pci.tex
index 044c085..6e0cb45 100644
--- a/transport-pci.tex
+++ b/transport-pci.tex
@@ -1148,4 +1148,3 @@ \subsubsection{Driver Handling Interrupts}\label{sec:Virtio Transport Options /
         re-examine the configuration space to see what changed.
     \end{itemize}
 \end{itemize}
-
-- 
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

[virtio-dev] Re: [virtio-comment] [PATCH 1/3] transport-pci: Remove empty line at end of file

[David Edmondson]

Parav Pandit <parav@nvidia.com> writes:

> Remove empty line at end of file.
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>

Reviewed-by: David Edmondson <david.edmondson@oracle.com>

> ---
>  transport-pci.tex | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/transport-pci.tex b/transport-pci.tex
> index 044c085..6e0cb45 100644
> --- a/transport-pci.tex
> +++ b/transport-pci.tex
> @@ -1148,4 +1148,3 @@ \subsubsection{Driver Handling Interrupts}\label{sec:Virtio Transport Options /
>          re-examine the configuration space to see what changed.
>      \end{itemize}
>  \end{itemize}
> -
> -- 
> 2.26.2
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
-- 
You bring light in.

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

[virtio-dev] Re: [PATCH 1/3] transport-pci: Remove empty line at end of file

[Michael S. Tsirkin]

On Fri, Mar 24, 2023 at 04:35:32AM +0300, Parav Pandit wrote:
> Remove empty line at end of file.
> 
> Signed-off-by: Parav Pandit <parav@nvidia.com>

Applied this one.

> ---
>  transport-pci.tex | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/transport-pci.tex b/transport-pci.tex
> index 044c085..6e0cb45 100644
> --- a/transport-pci.tex
> +++ b/transport-pci.tex
> @@ -1148,4 +1148,3 @@ \subsubsection{Driver Handling Interrupts}\label{sec:Virtio Transport Options /
>          re-examine the configuration space to see what changed.
>      \end{itemize}
>  \end{itemize}
> -
> -- 
> 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

[virtio-dev] [PATCH 2/3] transport-pci: Improve config msix vector description

[Parav Pandit]

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>
---
 transport-pci.tex | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/transport-pci.tex b/transport-pci.tex
index 6e0cb45..1bc89b4 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 for receiving
+        Configuration change interrupts.
 
 \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

[virtio-dev] [PATCH 3/3] transport-pci: Improve queue msix vector register desc

[Parav Pandit]

queue_msix_vector register is for receiving interrupts from the device
for the virtqueue.

"for MSI-X" is confusing term.

Also it is the register that driver "writes" to, similar to
many other registers such as queue_desc, queue_driver etc.

Hence, replace the verb from use to write.

Signed-off-by: Parav Pandit <parav@nvidia.com>
Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
---
 transport-pci.tex | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/transport-pci.tex b/transport-pci.tex
index 1bc89b4..9d492d5 100644
--- a/transport-pci.tex
+++ b/transport-pci.tex
@@ -367,7 +367,8 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
         A 0 means the queue is unavailable.
 
 \item[\field{queue_msix_vector}]
-        The driver uses this to specify the queue vector for MSI-X.
+        The driver writes an MSI-X vector number for receiving
+        virtqueue interrupts.
 
 \item[\field{queue_enable}]
         The driver uses this to selectively prevent the device from executing requests from this virtqueue.
-- 
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

[virtio-dev] Re: [PATCH 3/3] transport-pci: Improve queue msix vector register desc

[Michael S. Tsirkin]

On Fri, Mar 24, 2023 at 04:35:34AM +0300, Parav Pandit wrote:
> queue_msix_vector register is for receiving interrupts from the device
> for the virtqueue.
> 
> "for MSI-X" is confusing term.
> 
> Also it is the register that driver "writes" to, similar to
> many other registers such as queue_desc, queue_driver etc.
> 
> Hence, replace the verb from use to write.
> 
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
>  transport-pci.tex | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/transport-pci.tex b/transport-pci.tex
> index 1bc89b4..9d492d5 100644
> --- a/transport-pci.tex
> +++ b/transport-pci.tex
> @@ -367,7 +367,8 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>          A 0 means the queue is unavailable.
>  
>  \item[\field{queue_msix_vector}]
> -        The driver uses this to specify the queue vector for MSI-X.
> +        The driver writes an MSI-X vector number for receiving
> +        virtqueue interrupts.

Ok but "receiving" is confusing here. And the verb writes seems
to ask for direction, look at queue_desc as an example.

Following that example:

	The driver writes the MSI-X vector number used for virtqueue interrupts here.

would you agree?



>  \item[\field{queue_enable}]
>          The driver uses this to selectively prevent the device from executing requests from this virtqueue.
> -- 
> 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

[virtio-dev] RE: [PATCH 3/3] transport-pci: Improve queue msix vector register desc

[Parav Pandit]

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Tuesday, April 4, 2023 3:21 AM

> Ok but "receiving" is confusing here. And the verb writes seems to ask for
> direction, look at queue_desc as an example.
> 
What is the confusion in receiving?
Driver some reason is configuring queue's vector even if it doesn't want to "receive" interrupts?
Do you mean it is more verbose?

Word here "here" isn't necessary when describing the register itself, though it exists at other places.

> Following that example:
> 
> 	The driver writes the MSI-X vector number used for virtqueue
> interrupts here.
> 
Since a specific number is used here, article "an" is appropriate one.

> would you agree?

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

[virtio-dev] Re: [PATCH 3/3] transport-pci: Improve queue msix vector register desc

[Michael S. Tsirkin]

On Tue, Apr 04, 2023 at 06:14:20PM +0000, Parav Pandit wrote:
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Tuesday, April 4, 2023 3:21 AM
> 
> > Ok but "receiving" is confusing here. And the verb writes seems to ask for
> > direction, look at queue_desc as an example.
> > 
> What is the confusion in receiving?
> Driver some reason is configuring queue's vector even if it doesn't want to "receive" interrupts?
> Do you mean it is more verbose?

I mean driver does not even receive interrupts, APIC does.


> Word here "here" isn't necessary when describing the register itself, though it exists at other places.

if nothing else let's be consistent. without here it is not immediately clear
weather it's the register that is written to or the value specified
is written somewhere else.

> > Following that example:
> > 
> > 	The driver writes the MSI-X vector number used for virtqueue
> > interrupts here.
> > 
> Since a specific number is used here, article "an" is appropriate one.

No because it's the specific value used for interrupts.
Again, check other examples.

> > would you agree?


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

[virtio-dev] Re: [virtio-comment] [PATCH 0/3] transport-pci: msix summary update

[Xuan Zhuo]

Series:

Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>

On Fri, 24 Mar 2023 04:35:31 +0300, Parav Pandit <parav@nvidia.com> wrote:
> Summary for config_msix_vector and queue_msix_vector
> registers have a confusing text of "for MSI-X".
>
> Rewrite the register summary line.
>
> Patch summary:
> patch 1 removes empty line at the end of the file
> patch 2 updates configuration vector summary
> patch 3 updates queue vector summary
>
> These are only editorial changes to rewrite the summary.
> Hence it should not require a github issue.
>
> Parav Pandit (3):
>   transport-pci: Remove empty line at end of file
>   transport-pci: Improve config msix vector description
>   transport-pci: Improve queue msix vector register desc
>
>  transport-pci.tex | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> --
> 2.26.2
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
>

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

[virtio-dev] RE: [virtio-comment] [PATCH 0/3] transport-pci: msix summary update

[Parav Pandit]

Hi Cornelia,

> From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> Sent: Monday, March 27, 2023 2:09 AM
> Series:
> 
> Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> 

It is editorial change rewording the text.
Can you please take this short series forward?

> On Fri, 24 Mar 2023 04:35:31 +0300, Parav Pandit <parav@nvidia.com> wrote:
> > Summary for config_msix_vector and queue_msix_vector registers have a
> > confusing text of "for MSI-X".
> >
> > Rewrite the register summary line.
> >
> > Patch summary:
> > patch 1 removes empty line at the end of the file patch 2 updates
> > configuration vector summary patch 3 updates queue vector summary
> >
> > These are only editorial changes to rewrite the summary.
> > Hence it should not require a github issue.
> >
> > Parav Pandit (3):
> >   transport-pci: Remove empty line at end of file
> >   transport-pci: Improve config msix vector description
> >   transport-pci: Improve queue msix vector register desc
> >
> >  transport-pci.tex | 7 ++++---
> >  1 file changed, 4 insertions(+), 3 deletions(-)
> >
> > --
> > 2.26.2
> >
> >
> > This publicly archived list offers a means to provide input to the
> > OASIS Virtual I/O Device (VIRTIO) TC.
> >
> > In order to verify user consent to the Feedback License terms and to
> > minimize spam in the list archive, subscription is required before
> > posting.
> >
> > Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> > Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> > List help: virtio-comment-help@lists.oasis-open.org
> > List archive: https://lists.oasis-open.org/archives/virtio-comment/
> > Feedback License:
> > https://www.oasis-open.org/who/ipr/feedback_license.pdf
> > List Guidelines:
> > https://www.oasis-open.org/policies-guidelines/mailing-lists
> > Committee: https://www.oasis-open.org/committees/virtio/
> > Join OASIS: https://www.oasis-open.org/join/
> >

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

[virtio-dev] RE: [virtio-comment] [PATCH 0/3] transport-pci: msix summary update

[Cornelia Huck]

On Mon, Apr 03 2023, Parav Pandit <parav@nvidia.com> wrote:

> Hi Cornelia,
>
>> From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
>> Sent: Monday, March 27, 2023 2:09 AM
>> Series:
>> 
>> Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
>> 
>
> It is editorial change rewording the text.
> Can you please take this short series forward?

Patch 1 (which Michael has already pushed) is editorial; for the other
two patches, I'm not that sure, especially as there still seems to be
some discussion?


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