public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	"david.edmondson@oracle.com" <david.edmondson@oracle.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"sburla@marvell.com" <sburla@marvell.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	Yishai Hadas <yishaih@nvidia.com>,
	Maor Gottlieb <maorg@nvidia.com>,
	Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v10 4/4] transport-pci: Introduce group legacy group member config region access
Date: Thu, 6 Jul 2023 12:50:59 -0400	[thread overview]
Message-ID: <20230706125001-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481FC84712B83663691BB5FDC2CA@PH0PR12MB5481.namprd12.prod.outlook.com>

On Thu, Jul 06, 2023 at 04:45:50PM +0000, Parav Pandit wrote:
> 
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Thursday, July 6, 2023 12:39 PM
> 
> > > > +The group owner device or the group member device or both MAY
> > > > +support driver notifications region.
> > >
> > > Make this "a driver notification region"?
> > 
> > I think in fact for conformance we can just refer to supporting the command.
> > The command can return an array of structures, each referring to the memory
> > of the owner device or the member device.
> >
> Array and referring to owner/member is already present in this patch.


I don't see a statement that devices MAY support VIRTIO_ADMIN_CMD_LEGACY_NOTIFY_QUERY
with entries returning just owner, just member, or both.

> Do you suggest to drop above statement?

> > 
> > > > +
> > > > +For the SR-IOV group type, the owner device supporting
> > > > +VIRTIO_ADMIN_CMD_LEGACY_COMMON_CFG_READ,
> > > > +VIRTIO_ADMIN_CMD_LEGACY_COMMON_CFG_WRITE,
> > > > +VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_READ,
> > > > +VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_WRITE and
> > > > +VIRTIO_ADMIN_CMD_LEGACY_NOTIFY_QUERY
> > > > +commands and its member device SHOULD follow the rules for the PCI
> > > > +Device ID,
> > 
> > what does "its" mean here? Of the group?
> Yes, will change to the member device of the group.
> 
> > Members of the SR-IOV group type are VFs. They can not follow the rules for
> > the Device ID: the spec says:
> > This field in all VFs returns FFFFh when read.
> > 
> > Even if you somehow refer to the software it's extraneous anyway since the
> > spec proceeds: VI software should return the Vendor ID value from the
> > associated PF as the Vendor ID value for the VF.
> > 
> > We'll need a separate statement for Device ID.
> >
> Will split the line for Device ID.
>  
> > > > +Revision ID and Subsystem Device ID of the non-transitional devices
> > > > +documented in section \ref{sec:Virtio Transport Options / Virtio Over PCI
> > Bus / PCI Device Discovery}.


---------------------------------------------------------------------
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-06 16:51 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  4:17 [virtio-dev] [PATCH v10 0/4] admin: Access legacy registers using admin commands Parav Pandit
2023-07-06  4:17 ` [virtio-dev] [PATCH v10 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-07-06  4:17 ` [virtio-dev] [PATCH v10 2/4] admin: Fix section numbering Parav Pandit
2023-07-06 13:39   ` [virtio-dev] " Cornelia Huck
2023-07-06  4:17 ` [virtio-dev] [PATCH v10 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-07-06 16:12   ` [virtio-dev] " Cornelia Huck
2023-07-06 16:16     ` [virtio-dev] " Parav Pandit
2023-07-06  4:17 ` [virtio-dev] [PATCH v10 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-07-06 16:28   ` [virtio-dev] " Cornelia Huck
2023-07-06 16:33     ` [virtio-dev] " Parav Pandit
2023-07-06 16:42       ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 16:58         ` [virtio-dev] " Parav Pandit
2023-07-06 17:33           ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 17:47             ` [virtio-dev] " Parav Pandit
2023-07-06 18:06               ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 18:16                 ` [virtio-dev] " Parav Pandit
2023-07-06 18:48                   ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 18:53                     ` [virtio-dev] " Parav Pandit
2023-07-06 18:56                       ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 19:00                         ` [virtio-dev] " Parav Pandit
2023-07-06 19:42                           ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 20:21                             ` [virtio-dev] " Parav Pandit
2023-07-06 20:28                               ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 20:35                                 ` [virtio-dev] " Parav Pandit
2023-07-06 20:41                                   ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 20:43                                     ` [virtio-dev] " Parav Pandit
2023-07-07  8:12                                       ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
2023-07-07  8:32                                         ` Michael S. Tsirkin
2023-07-06 17:38           ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 16:47       ` [virtio-dev] " Cornelia Huck
2023-07-06 16:52         ` Parav Pandit
2023-07-06 16:39     ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 16:45       ` [virtio-dev] " Parav Pandit
2023-07-06 16:50         ` Michael S. Tsirkin [this message]
2023-07-06 16:54           ` Parav Pandit
2023-07-06 19:00   ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 19:07     ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
2023-07-06 19:59       ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 20: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=20230706125001-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=david.edmondson@oracle.com \
    --cc=jasowang@redhat.com \
    --cc=maorg@nvidia.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