From: Cornelia Huck <cohuck@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] Re: [PATCH V2] virtio-net: introduce admin control virtqueue
Date: Fri, 29 Jan 2021 11:57:37 +0100 [thread overview]
Message-ID: <20210129115737.77ea06c5.cohuck@redhat.com> (raw)
In-Reply-To: <e752ecaa-e04c-ecdc-3921-470942a71276@redhat.com>
On Thu, 28 Jan 2021 10:58:49 +0800
Jason Wang <jasowang@redhat.com> wrote:
> On 2021/1/27 下午6:59, Michael S. Tsirkin wrote:
> > Thus, an idea. How about controlling features instead?
> >
> > And with that, the interface becomes generic and applicable
> > to all devices not just net ...
>
>
> Yes, so I think we probably need more than this e.g I had plan to
> introduce a general admin virtqueue which could be use to replace the
> transport specific way to configure/probe virtual devices. I think we
> can add this new features controlling command via that virtqueue.
>
> So if this makes sense. I will drop the trust command in this patch and
> let admin cvq go first. Then I can post general admin virtqueue patch.
>
> Does this make sense?
So, you'd introduce a generic admin virtqueue and give individual
device types the possibility to use it for device type specific
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/
next prev parent reply other threads:[~2021-01-29 10:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 5:52 [virtio-comment] [PATCH V2] virtio-net: introduce admin control virtqueue Jason Wang
2021-01-25 6:31 ` Haozhong Zhang
2021-01-25 6:45 ` Jason Wang
2021-01-25 7:05 ` Haozhong Zhang
2021-01-25 7:48 ` Jason Wang
2021-01-25 10:22 ` Haozhong Zhang
2021-01-27 3:21 ` Jason Wang
2021-01-25 12:54 ` [virtio-comment] " Cornelia Huck
2021-01-27 3:30 ` Jason Wang
2021-01-27 8:48 ` Michael S. Tsirkin
2021-01-27 10:59 ` Michael S. Tsirkin
2021-01-28 2:58 ` Jason Wang
2021-01-29 10:57 ` Cornelia Huck [this message]
2021-02-01 3:42 ` Jason Wang
2021-02-01 16:10 ` Cornelia Huck
2021-01-29 22:48 ` [virtio-comment] " Halil Pasic
2021-02-01 4:09 ` Jason Wang
2021-02-01 15:49 ` Cornelia Huck
2021-02-02 3:28 ` 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=20210129115737.77ea06c5.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox