queue_msix_vector register is for receiving virtqueue notification
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 <pa...@nvidia.com>
Reviewed-by: Max Gurtovoy <mgurto...@nvidia.com>
---
changelog:
v1->v2:
- rewrote to indicate MSI-X table entry index
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 cf2c54d..afa082f 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 the MSI-X table entry index in this field for
+ virtqueue notification 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-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
