From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: "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: [virtio-comment] [PATCH v9 0/4] admin: Access legacy registers using admin commands
Date: Wed, 05 Jul 2023 15:42:40 +0200 [thread overview]
Message-ID: <87a5wa325r.fsf@redhat.com> (raw)
In-Reply-To: <PH0PR12MB5481B4761D5B67B850755782DC2FA@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Jul 05 2023, Parav Pandit <parav@nvidia.com> wrote:
>> From: Michael S. Tsirkin <mst@redhat.com>
>> Sent: Wednesday, July 5, 2023 7:09 AM
>>
>> OK I sent a bunch of comments. Pls try to address, unfortunately I didn't go in
>> depth over the last patch, but I feel it should be squashed into the generic
>> legacy command sections avoiding need for indirection, so rewriting it now
>> wouldn't be efficient.
>
> I relooked at well yday.
> Transport has very small section.
> This aligns to how the existing spec is written, for example vq notify data is explained in generic way and defined in pci way in PCI chapter.
> The indirection is fine and also self-contained similarly here.
Would it make sense to do this the other way around (i.e. use something
that is PCI-only from the start?)
IIUC, the "legacy" problem as it stands is something specific to PCI,
with MMIO using two distinct approaches for pre-1.0 and 1.0+, and CCW
simply using different commands (and no need for any kind of cross
access.) Not 100% sure about MMIO, but I don't think we need a version
of this for CCW.
---------------------------------------------------------------------
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-07-05 13:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 23:37 [virtio-dev] [PATCH v9 0/4] admin: Access legacy registers using admin commands Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-07-05 10:05 ` [virtio-dev] " Cornelia Huck
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 2/4] admin: Fix section numbering Parav Pandit
2023-07-05 10:09 ` [virtio-dev] " Cornelia Huck
2023-07-05 16:29 ` Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-07-05 10:24 ` [virtio-dev] " Cornelia Huck
2023-07-05 16:34 ` [virtio-dev] " Parav Pandit
2023-07-06 5:43 ` [virtio-dev] " Michael S. Tsirkin
2023-07-05 11:04 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-07-05 18:26 ` [virtio-dev] " Parav Pandit
2023-07-06 6:01 ` [virtio-dev] " Michael S. Tsirkin
2023-07-05 22:01 ` [virtio-dev] " Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-07-05 10:29 ` [virtio-dev] " Cornelia Huck
2023-07-05 16:36 ` [virtio-dev] " Parav Pandit
2023-07-05 10:56 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-07-05 11:09 ` [virtio-dev] Re: [virtio-comment] [PATCH v9 0/4] admin: Access legacy registers using admin commands Michael S. Tsirkin
2023-07-05 13:01 ` [virtio-dev] " Parav Pandit
2023-07-05 13:42 ` Cornelia Huck [this message]
2023-07-05 14:37 ` Parav Pandit
2023-07-06 4:20 ` Parav Pandit
2023-07-06 6:10 ` [virtio-dev] " Michael S. Tsirkin
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=87a5wa325r.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=jasowang@redhat.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.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