From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.oasis-open.org, david.edmondson@oracle.com,
virtio-dev@lists.oasis-open.org, sburla@marvell.com,
jasowang@redhat.com, yishaih@nvidia.com, maorg@nvidia.com,
shahafs@nvidia.com
Subject: [virtio-comment] Re: [PATCH v11 0/3] admin: Access legacy registers using admin commands
Date: Fri, 07 Jul 2023 13:37:08 +0200 [thread overview]
Message-ID: <87sfa00x7f.fsf@redhat.com> (raw)
In-Reply-To: <20230706183617-mutt-send-email-mst@kernel.org>
On Thu, Jul 06 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Fri, Jul 07, 2023 at 12:27:19AM +0300, Parav Pandit wrote:
>> 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.
>
> corneli want to apply 1,2 as editorial?
I guess that makes sense to get them out of the way.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.oasis-open.org, david.edmondson@oracle.com,
virtio-dev@lists.oasis-open.org, sburla@marvell.com,
jasowang@redhat.com, yishaih@nvidia.com, maorg@nvidia.com,
shahafs@nvidia.com
Subject: [virtio-dev] Re: [PATCH v11 0/3] admin: Access legacy registers using admin commands
Date: Fri, 07 Jul 2023 13:37:08 +0200 [thread overview]
Message-ID: <87sfa00x7f.fsf@redhat.com> (raw)
In-Reply-To: <20230706183617-mutt-send-email-mst@kernel.org>
On Thu, Jul 06 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Fri, Jul 07, 2023 at 12:27:19AM +0300, Parav Pandit wrote:
>> 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.
>
> corneli want to apply 1,2 as editorial?
I guess that makes sense to get them out of the way.
---------------------------------------------------------------------
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-07 11:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 21:27 [virtio-comment] [PATCH v11 0/3] admin: Access legacy registers using admin commands Parav Pandit
2023-07-06 21:27 ` [virtio-dev] " Parav Pandit
2023-07-06 21:27 ` [virtio-comment] [PATCH v11 1/3] admin: Split opcode table rows with a line Parav Pandit
2023-07-06 21:27 ` [virtio-dev] " Parav Pandit
2023-07-06 21:27 ` [virtio-comment] [PATCH v11 2/3] admin: Fix section numbering Parav Pandit
2023-07-06 21:27 ` [virtio-dev] " Parav Pandit
2023-07-06 21:27 ` [virtio-comment] [PATCH v11 3/3] admin: Add group member legacy register access commands Parav Pandit
2023-07-06 21:27 ` [virtio-dev] " Parav Pandit
2023-07-06 22:36 ` [virtio-comment] " Michael S. Tsirkin
2023-07-06 22:36 ` [virtio-dev] " Michael S. Tsirkin
2023-07-07 3:54 ` [virtio-comment] " Parav Pandit
2023-07-07 3:54 ` [virtio-dev] " Parav Pandit
2023-07-07 8:29 ` [virtio-comment] " Michael S. Tsirkin
2023-07-07 8:29 ` [virtio-dev] " Michael S. Tsirkin
2023-07-06 22:36 ` [virtio-comment] Re: [PATCH v11 0/3] admin: Access legacy registers using admin commands Michael S. Tsirkin
2023-07-06 22:36 ` [virtio-dev] " Michael S. Tsirkin
2023-07-07 11:37 ` Cornelia Huck [this message]
2023-07-07 11:37 ` Cornelia Huck
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=87sfa00x7f.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.