From: Parav Pandit <parav@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.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 v7 3/4] admin: Add group member legacy register access commands
Date: Thu, 29 Jun 2023 22:10:53 +0000 [thread overview]
Message-ID: <PH0PR12MB548186C2583259967459E3C9DC25A@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230629180620-mutt-send-email-mst@kernel.org>
> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Thursday, June 29, 2023 6:08 PM
[..]
> > Ok. For v8 I will have link and keep in pci transport section. Later I can move as
> union if needed.
>
> I can do that too.
>
Ok.
If you can merge the first two editorial fixes, I can drop them from v8.
I didn't attach github issue in those first two patches.
> > SIOV for PCI and CXL will look very different, so SIOV legacy I am not expecting
> any change for these commands.
>
> SIOV will need a notification structure within BAR, and it could reuse the same
> one.
>
> > > Also look at virtio_pci_notify_cap and check whether any normative
> > > statements there should apply here. Alignment I guess?
> >
> > I will move below normative from pci to generic.
> >
> > The group member driver SHOULD use the notification region supplied by the
> group owner driver.
>
> By owner device.
>
Ok.
> --
> MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-06-29 22:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 21:10 [virtio-dev] [PATCH v7 0/4] admin: Introduce legacy registers access using AQ Parav Pandit
2023-06-27 21:10 ` [virtio-dev] [PATCH v7 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-06-27 21:10 ` [virtio-dev] [PATCH v7 2/4] admin: Fix section numbering Parav Pandit
2023-06-27 21:10 ` [virtio-dev] [PATCH v7 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-06-29 19:50 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:32 ` [virtio-dev] " Parav Pandit
2023-06-29 21:45 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:50 ` [virtio-dev] " Parav Pandit
2023-06-29 21:56 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 22:02 ` [virtio-dev] " Parav Pandit
2023-06-29 22:07 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 22:10 ` Parav Pandit [this message]
2023-06-27 21:10 ` [virtio-dev] [PATCH v7 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-06-29 19:43 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:28 ` [virtio-dev] " Parav Pandit
2023-06-29 19:53 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:26 ` [virtio-dev] " Parav Pandit
2023-06-29 19:41 ` [virtio-dev] Re: [PATCH v7 0/4] admin: Introduce legacy registers access using AQ Michael S. Tsirkin
2023-06-29 21:27 ` [virtio-dev] " Parav Pandit
2023-06-29 19:57 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:36 ` [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=PH0PR12MB548186C2583259967459E3C9DC25A@PH0PR12MB5481.namprd12.prod.outlook.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).