Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
	cohuck@redhat.com, sgarzare@redhat.com, stefanha@redhat.com,
	nrupal.jani@intel.com, Piotr.Uminski@intel.com,
	hang.yuan@intel.com
Cc: virtio@lists.oasis-open.org, Jiri Pirko <jiri@nvidia.com>,
	Zhu Lingshan <lingshan.zhu@intel.com>,
	pasic@linux.ibm.com, Shahaf Shuler <shahafs@nvidia.com>,
	Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [virtio-comment] Re: [PATCH v12 00/10] Introduce device group and device management
Date: Mon, 24 Apr 2023 17:34:18 -0400	[thread overview]
Message-ID: <96083133-31eb-1c6e-e057-94dc97173f06@nvidia.com> (raw)
In-Reply-To: <cover.1682354275.git.mst@redhat.com>



On 4/24/2023 12:44 PM, Michael S. Tsirkin wrote:
> comments on previous one have all been minor, so I hope
> this means we are close to merging this.
> 
> Change log:
> 
> since 11:
> 	one "breaking" change in response to stefan's comment:
> 	in patch 5, num_queues has been specified not to include admin
> 	queues: just regular ones.
+1.
This will enable pci driver to dynamically enable the AQ without 
depending on upper layer driver.

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/


  parent reply	other threads:[~2023-04-24 21:35 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 16:44 [virtio-comment] [PATCH v12 00/10] Introduce device group and device management Michael S. Tsirkin
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 01/10] virtio: document forward compatibility guarantees Michael S. Tsirkin
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 02/10] admin: introduce device group and related concepts Michael S. Tsirkin
2023-04-24 21:02   ` [virtio-comment] " Max Gurtovoy
2023-04-24 21:47   ` Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 03/10] admin: introduce group administration commands Michael S. Tsirkin
2023-04-24 21:29   ` [virtio-comment] " Max Gurtovoy
2023-04-24 21:33     ` Michael S. Tsirkin
2023-04-24 22:07   ` Parav Pandit
2023-04-25  6:20     ` Michael S. Tsirkin
2023-04-25 13:25       ` [virtio-comment] " Parav Pandit
2023-04-25 13:31         ` [virtio-comment] " Michael S. Tsirkin
2023-04-25 13:38           ` [virtio-comment] " Parav Pandit
2023-04-25 20:04             ` [virtio-comment] " Michael S. Tsirkin
2023-04-25 20:18               ` [virtio-comment] " Parav Pandit
2023-04-25 20:55                 ` [virtio-comment] " Michael S. Tsirkin
2023-04-26 18:18                   ` Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 04/10] admin: introduce virtio admin virtqueues Michael S. Tsirkin
2023-04-24 22:32   ` [virtio-comment] " Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 05/10] pci: add admin vq registers to virtio over pci Michael S. Tsirkin
2023-04-24 22:06   ` [virtio-comment] " Max Gurtovoy
2023-04-24 22:14     ` Parav Pandit
2023-04-26 21:12       ` Max Gurtovoy
2023-04-26 22:11         ` [virtio-comment] " Parav Pandit
2023-04-26 22:31           ` [virtio-comment] " Max Gurtovoy
2023-04-27  0:11             ` [virtio-comment] " Parav Pandit
2023-05-05 15:12               ` [virtio-comment] " Michael S. Tsirkin
2023-05-05 15:14                 ` [virtio-comment] " Parav Pandit
2023-04-27 17:57             ` [virtio-comment] " Michael S. Tsirkin
2023-04-27 18:50               ` Max Gurtovoy
2023-05-05 15:22           ` Michael S. Tsirkin
2023-05-05 15:25             ` [virtio-comment] " Parav Pandit
2023-04-24 22:29   ` [virtio-comment] " Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 06/10] mmio: document ADMIN_VQ as reserved Michael S. Tsirkin
2023-04-24 22:08   ` [virtio-comment] " Max Gurtovoy
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 07/10] ccw: " Michael S. Tsirkin
2023-04-24 22:09   ` [virtio-comment] " Max Gurtovoy
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 08/10] admin: command list discovery Michael S. Tsirkin
2023-04-24 22:27   ` [virtio-comment] " Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 09/10] admin: conformance clauses Michael S. Tsirkin
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 10/10] ccw: document more reserved features Michael S. Tsirkin
2023-04-24 22:17   ` [virtio-comment] " Parav Pandit
2023-04-24 21:34 ` Parav Pandit [this message]
2023-05-02  7:51 ` [virtio-comment] Re: [virtio] [PATCH v12 00/10] Introduce device group and device management David Edmondson

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=96083133-31eb-1c6e-e057-94dc97173f06@nvidia.com \
    --to=parav@nvidia.com \
    --cc=Piotr.Uminski@intel.com \
    --cc=cohuck@redhat.com \
    --cc=hang.yuan@intel.com \
    --cc=jasowang@redhat.com \
    --cc=jiri@nvidia.com \
    --cc=lingshan.zhu@intel.com \
    --cc=mgurtovoy@nvidia.com \
    --cc=mst@redhat.com \
    --cc=nrupal.jani@intel.com \
    --cc=pasic@linux.ibm.com \
    --cc=sgarzare@redhat.com \
    --cc=shahafs@nvidia.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtio@lists.oasis-open.org \
    /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