From: "Michael S. Tsirkin" <mst@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
Jason Wang <jasowang@redhat.com>,
virtio-comment@lists.oasis-open.org, stefanha@redhat.com,
oren@nvidia.com, parav@nvidia.com, shahafs@nvidia.com,
eperezma@redhat.com, aadam@redhat.com, bodong@nvidia.com,
amikheev@nvidia.com
Subject: Re: [RFC PATCH v2 1/2] Add virtio Admin Virtqueue specification
Date: Mon, 2 Aug 2021 13:28:09 -0400 [thread overview]
Message-ID: <20210802132034-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <abbc3417-5636-4e06-d47b-123473f8bc4a@nvidia.com>
On Mon, Aug 02, 2021 at 06:27:58PM +0300, Max Gurtovoy wrote:
> The spec allows vendor specific stuff today that are not usable
Maybe start there and explain what are the issues you are
trying to address. I think there's a wide consensus in the
TC that significant features should be part of the spec
not a vendor specific thing. Existing vendor specific
capability is thus geared towards enabling minor extensions
such as bug work arounds.
> trying to create a usable API without adding one line of vendor code to
> driver.
Driver in the virtio terminology is taken widely to mean all software
interacting with the device through the virtio interface. Your
virtio-cli tool would be part of the driver.
--
MST
next prev parent reply other threads:[~2021-08-02 17:28 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 16:52 [RFC PATCH v2 1/2] Add virtio Admin Virtqueue specification Max Gurtovoy
2021-07-26 16:52 ` [RFC PATCH v2 2/2] virtio-blk: add support for VIRTIO_F_ADMIN_VQ Max Gurtovoy
2021-07-27 12:24 ` Stefan Hajnoczi
2021-07-27 16:08 ` [virtio-comment] " Max Gurtovoy
2021-07-28 8:25 ` Stefan Hajnoczi
2021-07-27 10:27 ` [RFC PATCH v2 1/2] Add virtio Admin Virtqueue specification Stefan Hajnoczi
2021-07-27 14:28 ` [virtio-comment] " Cornelia Huck
2021-07-27 15:29 ` Max Gurtovoy
2021-07-28 8:52 ` Stefan Hajnoczi
2021-07-28 10:59 ` Max Gurtovoy
2021-07-28 13:42 ` Stefan Hajnoczi
2021-07-28 14:20 ` Max Gurtovoy
2021-07-29 8:48 ` Stefan Hajnoczi
2021-08-01 10:46 ` [virtio-comment] " Max Gurtovoy
2021-08-02 12:58 ` Stefan Hajnoczi
2021-07-28 12:53 ` Michael S. Tsirkin
2021-07-30 6:45 ` [virtio-comment] " Cornelia Huck
2021-07-28 12:48 ` Michael S. Tsirkin
2021-07-29 14:51 ` Max Gurtovoy
2021-07-30 7:05 ` [virtio-comment] " Cornelia Huck
2021-07-31 11:34 ` Max Gurtovoy
2021-07-31 22:26 ` Michael S. Tsirkin
2021-07-31 22:53 ` Max Gurtovoy
2021-08-01 8:16 ` Michael S. Tsirkin
2021-08-01 8:38 ` Max Gurtovoy
2021-08-02 2:17 ` Jason Wang
2021-08-02 2:19 ` Jason Wang
2021-08-02 9:54 ` Max Gurtovoy
2021-08-02 14:51 ` [virtio-comment] " Cornelia Huck
2021-08-02 15:27 ` Max Gurtovoy
2021-08-02 17:28 ` Michael S. Tsirkin [this message]
2021-08-03 3:39 ` Jason Wang
2021-08-03 8:32 ` Max Gurtovoy
2021-08-03 9:01 ` Jason Wang
2021-08-03 9:21 ` Max Gurtovoy
2021-08-03 10:04 ` [virtio-comment] " Jason Wang
2021-07-30 7:36 ` Michael S. Tsirkin
2021-07-31 11:53 ` Max Gurtovoy
2021-07-31 22:17 ` Michael S. Tsirkin
2021-07-31 23:46 ` Max Gurtovoy
2021-08-02 13:22 ` Stefan Hajnoczi
2021-08-02 14:34 ` [virtio-comment] " Cornelia Huck
2021-08-02 14:58 ` Max Gurtovoy
2021-08-02 16:39 ` Stefan Hajnoczi
2021-08-02 15:21 ` [virtio-comment] " Cornelia Huck
2021-08-02 16:03 ` Max Gurtovoy
2021-08-02 17:05 ` Michael S. Tsirkin
2021-08-03 6:28 ` [virtio-comment] " Cornelia Huck
2021-08-03 6:41 ` Jason Wang
2021-08-03 6:51 ` [virtio-comment] " Cornelia Huck
2021-08-03 7:55 ` Max Gurtovoy
2021-08-03 8:55 ` Cornelia Huck
2021-08-03 9:04 ` Max Gurtovoy
2021-08-02 2:25 ` Jason Wang
2021-08-02 9:51 ` Max Gurtovoy
2021-08-02 17:07 ` Michael S. Tsirkin
2021-08-03 3:22 ` Jason Wang
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=20210802132034-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aadam@redhat.com \
--cc=amikheev@nvidia.com \
--cc=bodong@nvidia.com \
--cc=cohuck@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=mgurtovoy@nvidia.com \
--cc=oren@nvidia.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@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 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.