From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>, virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] Re: [PATCH V2] virtio-net: introduce admin control virtqueue
Date: Wed, 27 Jan 2021 03:48:03 -0500 [thread overview]
Message-ID: <20210127034559-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <7cba572c-0dcd-1b35-616b-a80629f2d4a8@redhat.com>
On Wed, Jan 27, 2021 at 11:30:14AM +0800, Jason Wang wrote:
> >
> > Does the management device get to choose if it wants to trust a virtual
> > device, i.e. can it fail enabling the trust?
>
>
> Yes, the idea is to let management device to choose which virtual device is
> trust. For the possible failure, I think we should allow the device to fail
> the enabling, e.g when the device is lacking resources for virtual devices
> (e.g mac address tables etc).
>
> Thanks
Wrt SRIOV at least, the standard model is to have the PF control VFs.
I am not saying trusting some VF instead has no uses but
unless someone requested it I'd stick to the standard model
initially.
--
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/
next prev parent reply other threads:[~2021-01-27 8:48 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 [this message]
2021-01-27 10:59 ` Michael S. Tsirkin
2021-01-28 2:58 ` Jason Wang
2021-01-29 10:57 ` Cornelia Huck
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=20210127034559-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=jasowang@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