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 3/4] admin: Add group member legacy register access commands
Date: Tue, 4 Jul 2023 18:17:03 -0400 [thread overview]
Message-ID: <20230704181622-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54817F7888F3FAA6F8874055DC2EA@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, Jul 04, 2023 at 10:15:34PM +0000, Parav Pandit wrote:
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Tuesday, July 4, 2023 6:01 PM
> >
> > In some systems, there's need to support utilizing legacy drivers with devices
> > that do not directly support the legacy interface.
> > In such scenarios, an owner device of a group can provide the legacy interface
> > functionality for group members.
> > The driver of an owner device can then access the legacy interface of a member
> > device on behalf of the legacy member device driver.
> >
> In the last line, I will change from 'legacy member device driver' to just 'member device driver'.
I think it's important to stress legacy since normal driver
that follows the spec does not access legacy interface at all.
> I will fix rest of the comments including having pad bytes after offset and have similar changes in rest of the places.
---------------------------------------------------------------------
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-04 22:17 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 ` Michael S. Tsirkin [this message]
2023-07-04 22:18 ` 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 ` [virtio-dev] " Michael S. Tsirkin
2023-07-04 16:10 ` [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=20230704181622-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