All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
	virtio-comment@lists.oasis-open.org, mst@redhat.com,
	david.edmondson@oracle.com
Cc: virtio-dev@lists.oasis-open.org, sburla@marvell.com,
	jasowang@redhat.com, yishaih@nvidia.com, maorg@nvidia.com,
	shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] Re: [PATCH v12 0/3] admin: Access legacy registers using admin commands
Date: Fri, 07 Jul 2023 13:46:18 +0200	[thread overview]
Message-ID: <87pm540ws5.fsf@redhat.com> (raw)
In-Reply-To: <20230707035401.107855-1-parav@nvidia.com>

On Fri, Jul 07 2023, Parav Pandit <parav@nvidia.com> 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.
>
> Patch summary:
> --------------
> patch-1 fix split rows of admin opcode tables by a line
> patch-2 fix section numbering

Pushed 1+2 as editorial updates.

> patch-3 add legacy region access commands


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: Parav Pandit <parav@nvidia.com>,
	virtio-comment@lists.oasis-open.org, mst@redhat.com,
	david.edmondson@oracle.com
Cc: virtio-dev@lists.oasis-open.org, sburla@marvell.com,
	jasowang@redhat.com, yishaih@nvidia.com, maorg@nvidia.com,
	shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v12 0/3] admin: Access legacy registers using admin commands
Date: Fri, 07 Jul 2023 13:46:18 +0200	[thread overview]
Message-ID: <87pm540ws5.fsf@redhat.com> (raw)
In-Reply-To: <20230707035401.107855-1-parav@nvidia.com>

On Fri, Jul 07 2023, Parav Pandit <parav@nvidia.com> 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.
>
> Patch summary:
> --------------
> patch-1 fix split rows of admin opcode tables by a line
> patch-2 fix section numbering

Pushed 1+2 as editorial updates.

> patch-3 add legacy region access commands


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  parent reply	other threads:[~2023-07-07 11:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  3:53 [virtio-comment] [PATCH v12 0/3] admin: Access legacy registers using admin commands Parav Pandit
2023-07-07  3:53 ` [virtio-dev] " Parav Pandit
2023-07-07  3:53 ` [virtio-comment] [PATCH v12 1/3] admin: Split opcode table rows with a line Parav Pandit
2023-07-07  3:53   ` [virtio-dev] " Parav Pandit
2023-07-07  3:54 ` [virtio-comment] [PATCH v12 2/3] admin: Fix section numbering Parav Pandit
2023-07-07  3:54   ` [virtio-dev] " Parav Pandit
2023-07-07  3:54 ` [virtio-comment] [PATCH v12 3/3] admin: Add group member legacy register access commands Parav Pandit
2023-07-07  3:54   ` [virtio-dev] " Parav Pandit
2023-07-07  9:30   ` [virtio-comment] " Michael S. Tsirkin
2023-07-07  9:30     ` [virtio-dev] " Michael S. Tsirkin
2023-07-07 13:26     ` [virtio-comment] " Parav Pandit
2023-07-07 13:26       ` [virtio-dev] " Parav Pandit
2023-07-07 14:17       ` [virtio-comment] " Michael S. Tsirkin
2023-07-07 14:17         ` [virtio-dev] " Michael S. Tsirkin
2023-07-07 14:18         ` [virtio-comment] " Parav Pandit
2023-07-07 14:18           ` [virtio-dev] " Parav Pandit
2023-07-07 15:32     ` [virtio-comment] " Parav Pandit
2023-07-07 15:32       ` [virtio-dev] " Parav Pandit
2023-07-07 11:46 ` Cornelia Huck [this message]
2023-07-07 11:46   ` [virtio-dev] Re: [PATCH v12 0/3] admin: Access legacy registers using admin commands Cornelia Huck
2023-07-07 15:31   ` [virtio-comment] " Parav Pandit
2023-07-07 15:31     ` [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=87pm540ws5.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.