public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: <mst@redhat.com>, <virtio-dev@lists.oasis-open.org>,
	<cohuck@redhat.com>, <david.edmondson@oracle.com>
Cc: <sburla@marvell.com>, <jasowang@redhat.com>, <yishaih@nvidia.com>,
	<maorg@nvidia.com>, <virtio-comment@lists.oasis-open.org>,
	<shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] [PATCH v2 2/2] transport-pci: Add legacy register access conformance section
Date: Sat, 6 May 2023 03:01:35 +0300	[thread overview]
Message-ID: <20230506000135.628899-3-parav@nvidia.com> (raw)
In-Reply-To: <20230506000135.628899-1-parav@nvidia.com>

Add device and driver conformanace section for legacy registers access
commands interface.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v1->v2:
- addressed comments from Michael
- removed duplicate and contradicting normatives to existing legacy
  interface section
- added endianness normative for device specific region
- updated conformance links
---
 conformance.tex               |  2 ++
 transport-pci-legacy-regs.tex | 27 +++++++++++++++++++++++++++
 2 files changed, 29 insertions(+)

diff --git a/conformance.tex b/conformance.tex
index 01ccd69..3f2d49e 100644
--- a/conformance.tex
+++ b/conformance.tex
@@ -109,6 +109,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \item \ref{drivernormative:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / PCI configuration access capability}
 \item \ref{drivernormative:Virtio Transport Options / Virtio Over PCI Bus / PCI-specific Initialization And Device Operation / Device Initialization / MSI-X Vector Configuration}
 \item \ref{drivernormative:Virtio Transport Options / Virtio Over PCI Bus / PCI-specific Initialization And Device Operation / Notification of Device Configuration Changes}
+\item \ref{drivernormative:Virtio Transport Options / Virtio Over PCI Bus / Legacy Interfaces: SR-IOV VFs Registers Access}
 \end{itemize}
 
 \conformance{\subsection}{MMIO Driver Conformance}\label{sec:Conformance / Driver Conformance / MMIO Driver Conformance}
@@ -194,6 +195,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \item \ref{devicenormative:Virtio Transport Options / Virtio Over PCI Bus / PCI-specific Initialization And Device Operation / Device Initialization / MSI-X Vector Configuration}
 \item \ref{devicenormative:Virtio Transport Options / Virtio Over PCI Bus / PCI-specific Initialization And Device Operation / Used Buffer Notifications}
 \item \ref{devicenormative:Virtio Transport Options / Virtio Over PCI Bus / PCI-specific Initialization And Device Operation / Notification of Device Configuration Changes}
+\item \ref{devicenormative:Virtio Transport Options / Virtio Over PCI Bus / Legacy Interfaces: SR-IOV VFs Registers Access}
 \end{itemize}
 
 \conformance{\subsection}{MMIO Device Conformance}\label{sec:Conformance / Device Conformance / MMIO Device Conformance}
diff --git a/transport-pci-legacy-regs.tex b/transport-pci-legacy-regs.tex
index 9088fe6..4db578f 100644
--- a/transport-pci-legacy-regs.tex
+++ b/transport-pci-legacy-regs.tex
@@ -104,3 +104,30 @@ \subsubsection{Legacy Queue Notify Offset Query Command}\label{sec:Virtio Transp
 interface I/O space BAR and passthrough other PCI BARs and PCI device
 capabilities to the guest virtual machine without any translation.
 \end{note}
+
+\devicenormative{\paragraph}{SR-IOV VFs Legacy Registers Access}{Virtio Transport Options / Virtio Over PCI Bus / Legacy Interfaces: SR-IOV VFs Registers Access}
+
+If the PCI PF device supports legacy registers access for its group members,
+the device MUST set all corresponding bits for commands VIRTIO_ADMIN_CMD_LREG_WRITE,
+VIRTIO_ADMIN_CMD_LREG_READ and VIRTIO_ADMIN_CMD_LQ_NOTIFY_QUERY in
+command result of VIRTIO_ADMIN_CMD_LIST_QUERY in
+\field{device_admin_cmd_opcodes}.
+
+The device MUST encode and decode legacy device specific registers using
+little-endian format.
+
+The device MUST fail VIRTIO_ADMIN_CMD_LREG_WRITE and VIRTIO_ADMIN_CMD_LREG_READ
+commands for the invalid offset which is outside the legacy registers
+address range.
+
+The PCI VF device SHOULD NOT use PCI BAR 0 when it prefers to support
+legacy interface registers access.
+
+\drivernormative{\paragraph}{SR-IOV VFs Legacy Registers Access}{Virtio Transport Options / Virtio Over PCI Bus / Legacy Interfaces: SR-IOV VFs Registers Access}
+
+The driver MUST encode and decode legacy device specific registers using
+little-endian format.
+
+The driver SHOULD send commands VIRTIO_ADMIN_CMD_LREG_WRITE and
+VIRTIO_ADMIN_CMD_LREG_READ with a valid offset which is in the legacy
+registers address range.
-- 
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


  parent reply	other threads:[~2023-05-06  0:02 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06  0:01 [virtio-dev] [PATCH v2 0/2] transport-pci: Introduce legacy registers access using AQ Parav Pandit
2023-05-06  0:01 ` [virtio-dev] [PATCH v2 1/2] transport-pci: Introduce legacy registers access commands Parav Pandit
2023-05-17  5:44   ` [virtio-dev] " Michael S. Tsirkin
2023-05-17 19:32     ` [virtio-dev] " Parav Pandit
2023-05-18 19:42       ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-05-18 20:51         ` [virtio-dev] " Parav Pandit
2023-05-19  1:54         ` [virtio-dev] " Jason Wang
2023-05-19  2:04           ` [virtio-dev] " Parav Pandit
2023-05-19  6:06         ` [virtio-dev] " Michael S. Tsirkin
2023-05-19 16:37           ` [virtio-dev] " Parav Pandit
2023-05-21  9:16             ` [virtio-dev] " Michael S. Tsirkin
2023-05-21 13:21               ` [virtio-dev] " Parav Pandit
2023-05-21 14:33                 ` [virtio-dev] " Michael S. Tsirkin
2023-05-21 14:44                   ` [virtio-dev] " Parav Pandit
2023-05-22 20:07                     ` [virtio-dev] " Michael S. Tsirkin
2023-05-22 21:05                       ` [virtio-dev] " Parav Pandit
2023-05-22 21:34                         ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 17:13                           ` [virtio-dev] " Parav Pandit
2023-05-23 18:48                             ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 22:22                               ` [virtio-dev] " Parav Pandit
2023-05-24  1:17                                 ` [virtio-dev] " Jason Wang
2023-05-24 10:07                                 ` Michael S. Tsirkin
2023-05-24 19:18                                   ` [virtio-dev] " Parav Pandit
2023-05-24 20:12                                     ` [virtio-dev] " Michael S. Tsirkin
2023-05-24 21:02                                       ` [virtio-dev] " Parav Pandit
2023-05-22 21:42                         ` [virtio-dev] " Michael S. Tsirkin
2023-05-22  0:54                   ` Jason Wang
2023-05-22  2:46                     ` [virtio-dev] " Parav Pandit
2023-05-22 19:35                     ` [virtio-dev] " Michael S. Tsirkin
2023-05-06  0:01 ` Parav Pandit [this message]
2023-05-06  2:31 ` [virtio-dev] Re: [PATCH v2 0/2] transport-pci: Introduce legacy registers access using AQ Jason Wang
2023-05-07 13:44   ` Michael S. Tsirkin
2023-05-08  2:23     ` Jason Wang
2023-05-08 17:07       ` Parav Pandit
2023-05-09  3:44         ` Jason Wang
2023-05-09  3:56           ` [virtio-dev] " Parav Pandit
2023-05-10  3:51             ` [virtio-dev] " Jason Wang
2023-05-10  4:22               ` Jason Wang
2023-05-10 16:07                 ` Parav Pandit
2023-05-11  7:20                   ` [virtio-dev] Re: [virtio-comment] " Jason Wang
2023-05-11 11:35                     ` Michael S. Tsirkin
2023-05-15  5:08                       ` Jason Wang
2023-05-15 15:25                     ` [virtio-dev] " Parav Pandit
2023-05-10 16:04               ` [virtio-dev] " Parav Pandit
2023-05-11  7:17                 ` Jason Wang
2023-05-11 14:31                   ` [virtio-dev] " Parav Pandit
2023-05-15  5:12                     ` [virtio-dev] Re: [virtio-comment] " Jason Wang
2023-05-15 15:26                       ` [virtio-dev] " Parav Pandit
2023-05-10  6:04       ` [virtio-dev] " Michael S. Tsirkin
2023-05-10  7:01         ` Jason Wang
2023-05-10  7:43           ` Michael S. Tsirkin
2023-05-10 16:13             ` Parav Pandit
2023-05-11  7:04             ` Jason Wang
2023-05-11 12:54               ` Michael S. Tsirkin
2023-05-11 13:02                 ` [virtio-dev] " Parav Pandit
2023-05-15  7:30                   ` [virtio-dev] " Jason Wang
2023-05-15 10:08                     ` Michael S. Tsirkin
2023-05-15 14:30                       ` [virtio-dev] " Parav Pandit
2023-05-23 18:16                         ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 21:32                           ` [virtio-dev] " Parav Pandit
2023-05-24  5:56                             ` [virtio-dev] " Michael S. Tsirkin
2023-05-24 18:57                               ` [virtio-dev] " Parav Pandit
2023-05-24 19:58                                 ` [virtio-dev] " Michael S. Tsirkin
2023-05-24 20:01                                   ` [virtio-dev] " Parav Pandit
2023-05-24 20:15                                     ` [virtio-dev] " Michael S. Tsirkin
2023-05-15 15:59                     ` [virtio-dev] " Parav Pandit
2023-05-16  6:21                       ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 19:11                         ` [virtio-dev] " Parav Pandit
2023-05-16 20:58                           ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 21:19                             ` [virtio-dev] " Parav Pandit
2023-05-16 21:23                               ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 21:30                                 ` [virtio-dev] " Parav Pandit
2023-05-15  7:13                 ` [virtio-dev] " Jason Wang
2023-05-11 13:15               ` [virtio-dev] " Parav Pandit
2023-05-11 13:45                 ` [virtio-dev] " Michael S. Tsirkin
2023-05-12 14:03                   ` Parav Pandit
2023-05-16  3:54                 ` Jason Wang
2023-05-16 19:35                   ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
2023-05-16 21:11                     ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 21:49                       ` [virtio-dev] " Parav Pandit
2023-05-16 21:56                         ` [virtio-dev] " Michael S. Tsirkin
2023-05-10 16:11         ` [virtio-dev] " Parav Pandit
2023-05-10 16:16           ` Michael S. Tsirkin
2023-05-10 17:33             ` [virtio-dev] " Parav Pandit
2023-05-10 21:08               ` Parav Pandit
2023-05-10 21:33                 ` [virtio-dev] " Michael S. Tsirkin
2023-05-10 21:48                   ` [virtio-dev] " Parav Pandit
2023-05-11  7:06                 ` [virtio-dev] " Jason Wang
2023-05-11 13:04                   ` Michael S. Tsirkin
2023-05-15  5:19                     ` Jason Wang
2023-05-15 15:31                       ` [virtio-dev] " Parav Pandit
2023-05-11 13:28                   ` Parav Pandit
2023-05-11 13:38                     ` [virtio-dev] " Michael S. Tsirkin
2023-05-11 16:00                       ` [virtio-dev] " Parav Pandit
2023-05-11 20:47                       ` Parav Pandit
2023-05-11 20:58                         ` [virtio-dev] " Michael S. Tsirkin
2023-05-11 21:03                           ` [virtio-dev] " Parav Pandit
2023-05-15 16:55                             ` Parav Pandit
2023-05-15  7:10                     ` [virtio-dev] " Jason Wang
2023-05-15 15:49                       ` [virtio-dev] " Parav Pandit
2023-05-15 17:44                         ` [virtio-dev] " Michael S. Tsirkin
2023-05-15 17:51                           ` [virtio-dev] " Parav Pandit
2023-05-15 17:56                             ` [virtio-dev] " Michael S. Tsirkin
2023-05-15 18:00                               ` [virtio-dev] " Parav Pandit
2023-05-15 18:01                                 ` [virtio-dev] " Michael S. Tsirkin
2023-05-15 18:05                                   ` [virtio-dev] " Parav Pandit
2023-05-16  3:37                                   ` [virtio-dev] " Jason Wang
2023-05-16  3:43                                     ` Jason Wang
2023-05-16  5:38                                       ` Michael S. Tsirkin
2023-05-16  3:28                         ` Jason Wang
2023-05-16  3:45                           ` [virtio-dev] " Parav Pandit
2023-05-16  4:08                             ` [virtio-dev] " Jason Wang
2023-05-16 19:29                               ` [virtio-dev] " Parav Pandit
2023-05-16 21:09                                 ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 21:41                                   ` [virtio-dev] " Parav Pandit
2023-05-16 21:54                                     ` [virtio-dev] " Michael S. Tsirkin
2023-05-16  4:18                           ` Michael S. Tsirkin
2023-05-07  9:04 ` Michael S. Tsirkin
2023-05-08 16:54   ` Parav Pandit
2023-05-15 20:29     ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-05-15 20:56       ` [virtio-dev] " Parav Pandit
2023-05-16  4:32         ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 18:45           ` [virtio-dev] " Parav Pandit
2023-05-16 20:42             ` [virtio-dev] " Michael S. Tsirkin
2023-05-23  6:38 ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 17: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=20230506000135.628899-3-parav@nvidia.com \
    --to=parav@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=david.edmondson@oracle.com \
    --cc=jasowang@redhat.com \
    --cc=maorg@nvidia.com \
    --cc=mst@redhat.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