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: "virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	"cohuck@redhat.com" <cohuck@redhat.com>,
	"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 v8 0/4] admin: Access legacy registers using admin commands
Date: Tue, 4 Jul 2023 11:40:46 -0400	[thread overview]
Message-ID: <20230704114012-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54811B4999A4249C55AAB41FDC2EA@PH0PR12MB5481.namprd12.prod.outlook.com>

On Tue, Jul 04, 2023 at 01:26:20PM +0000, Parav Pandit wrote:
> Hi Michael,
> 
> > From: Parav Pandit <parav@nvidia.com>
> > Sent: Friday, June 30, 2023 12:20 AM
> > 
> > This short series introduces legacy registers access commands for the owner
> > group member access the legacy registers of the member VFs.
> > This short series introduces legacy region access commands by the group owner
> > device for its member devices.
> > Currently it is applicable to the PCI PF and VF devices. If in future any SIOV
> > devices to support legacy registers, they can be easily supported using same
> > commands by using the group member identifiers of the future SIOV devices.
> > 
> > More details as overview, motivation, use case are further described below.
> > 
> > Patch summary:
> > --------------
> > patch-1 split rows of admin opcode tables by a line
> > patch-2 fix section numbering
> > patch-3 add generic legacy region access commands
> > patch-4 add pci specific definition
> 
> [..]
> > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/167
> > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > 
> > ---
> > changelog:
> > v7->v8:
> > - remove empty line at the end of file
> > - removed white space at the end
> > - addressed comments from Michael add link to pci
> > - renamed region to region_data
> > - made region_data width to be 16 bytes to cover for 8 bytes offset
> > - moved generic notification region related normative from pci to
> >   generic section
> > - made bar offset 64-bit
> > - prefix legacy specific structure with _legacy
> > - moved generic normative from pci to generic section
> > - added link to virtio pci capabilities when referring to bar 0
> > - remove 'should' from generic description
> 
> Do you have any further comments on 3rd and 4th patch?
> I fixed your comments of v7, and some more were fixed.


Hope to send review tonight, max tomorrow.


---------------------------------------------------------------------
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-04 15:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  4:20 [virtio-dev] [PATCH v8 0/4] admin: Access legacy registers using admin commands Parav Pandit
2023-06-30  4:20 ` [virtio-dev] [PATCH v8 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-06-30  4:20 ` [virtio-dev] [PATCH v8 2/4] admin: Fix section numbering Parav Pandit
2023-06-30  4:20 ` [virtio-dev] [PATCH v8 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-07-04 22:00   ` [virtio-dev] " Michael S. Tsirkin
2023-07-04 22:15     ` [virtio-dev] " Parav Pandit
2023-07-04 22:17       ` [virtio-dev] " Michael S. Tsirkin
2023-07-04 22:18         ` [virtio-dev] " Parav Pandit
2023-07-04 23:39     ` Parav Pandit
2023-06-30  4:20 ` [virtio-dev] [PATCH v8 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-07-04 13:26 ` [virtio-dev] RE: [PATCH v8 0/4] admin: Access legacy registers using admin commands Parav Pandit
2023-07-04 15:40   ` Michael S. Tsirkin [this message]
2023-07-04 16:10     ` 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=20230704114012-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