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 v7 3/4] admin: Add group member legacy register access commands
Date: Thu, 29 Jun 2023 17:56:53 -0400 [thread overview]
Message-ID: <20230629175234-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB548102851D796A39FEC61275DC25A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Thu, Jun 29, 2023 at 09:50:45PM +0000, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Thursday, June 29, 2023 5:46 PM
>
> > > > Or preferably I would just include that tex right here to avoid the
> > > > need to jump back and forth.
> > > >
> > > We have vq notify config data as generic and transport specific
> > > listing,
> >
> > But note how that is included directly in multiple places - not a link. In the
> > resulting PDF it appears inline.
>
> For notify data structure is not defined, so its little simpler.
> Here for AQ command structure is defined in the generic section as just bytes.
>
> I have mixed feelings; I think definition in transport and link in generic section is fine.
> Are you ok with that?
I am yet to focus on wording, can't tell you for sure. My gut feeling
is that keeping everything in one place would be more readable, will
help us converge more quickly, and the next user of admin commands is
expected to be SIOV which would need the same structure anyway (it's
also PCI).
Also look at virtio_pci_notify_cap and check whether any
normative statements there should apply here. Alignment I guess?
> >
> > > So will improve this part of text with link.
> >
> > anyway, that's not part of ABI.
---------------------------------------------------------------------
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 21:57 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 ` Michael S. Tsirkin [this message]
2023-06-29 22:02 ` Parav Pandit
2023-06-29 22:07 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 22:10 ` [virtio-dev] " Parav Pandit
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=20230629175234-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