All of lore.kernel.org
 help / color / mirror / Atom feed
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-comment] Re: [PATCH v12 3/3] admin: Add group member legacy register access commands
Date: Fri, 7 Jul 2023 10:17:08 -0400	[thread overview]
Message-ID: <20230707101650-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481B9E319B41225FEAE3BE7DC2DA@PH0PR12MB5481.namprd12.prod.outlook.com>

On Fri, Jul 07, 2023 at 01:26:56PM +0000, Parav Pandit wrote:
> 
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Friday, July 7, 2023 5:31 AM
> 
> [..]
> > > +For VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_WRITE and
> > > +VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_READ commands, the driver
> > SHOULD set
> > > +\field{offset} and the length of the \field{data} to refer to a
> > > +single field within the virtio device-specific configuration.
> > > +
> > > +If VIRTIO_ADMIN_CMD_LEGACY_NOTIFY_INFO command is supported, the
> > > +group member driver SHOULD use the notification address to send a
> > > +driver notification to the device.
> > 
> > No group member driver is not involved.
> Ok.
> 
> > Just say the driver. And "driver notifications" - you want this for all of them no?
> > 
> Didn’t understand the question. 
> Do you mean "all devices"?

all driver notifications.

-- 
MST


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: "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 v12 3/3] admin: Add group member legacy register access commands
Date: Fri, 7 Jul 2023 10:17:08 -0400	[thread overview]
Message-ID: <20230707101650-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481B9E319B41225FEAE3BE7DC2DA@PH0PR12MB5481.namprd12.prod.outlook.com>

On Fri, Jul 07, 2023 at 01:26:56PM +0000, Parav Pandit wrote:
> 
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Friday, July 7, 2023 5:31 AM
> 
> [..]
> > > +For VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_WRITE and
> > > +VIRTIO_ADMIN_CMD_LEGACY_DEV_CFG_READ commands, the driver
> > SHOULD set
> > > +\field{offset} and the length of the \field{data} to refer to a
> > > +single field within the virtio device-specific configuration.
> > > +
> > > +If VIRTIO_ADMIN_CMD_LEGACY_NOTIFY_INFO command is supported, the
> > > +group member driver SHOULD use the notification address to send a
> > > +driver notification to the device.
> > 
> > No group member driver is not involved.
> Ok.
> 
> > Just say the driver. And "driver notifications" - you want this for all of them no?
> > 
> Didn’t understand the question. 
> Do you mean "all devices"?

all driver notifications.

-- 
MST


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


  reply	other threads:[~2023-07-07 14:17 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       ` Michael S. Tsirkin [this message]
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 ` [virtio-comment] Re: [PATCH v12 0/3] admin: Access legacy registers using admin commands Cornelia Huck
2023-07-07 11:46   ` [virtio-dev] " 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=20230707101650-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 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.