[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180624044436-mutt-send-email-mst@kernel.org>
Date: Sun, 24 Jun 2018 04:45:36 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Siwei Liu <loseweigh@...il.com>
Cc: Cornelia Huck <cohuck@...hat.com>,
"Samudrala, Sridhar" <sridhar.samudrala@...el.com>,
Alexander Duyck <alexander.h.duyck@...el.com>,
virtio-dev@...ts.oasis-open.org, aaron.f.brown@...el.com,
Jiri Pirko <jiri@...nulli.us>, Jakub Kicinski <kubakici@...pl>,
Netdev <netdev@...r.kernel.org>, qemu-devel@...gnu.org,
virtualization@...ts.linux-foundation.org, konrad.wilk@...cle.com,
boris.ostrovsky@...cle.com,
Joao Martins <joao.m.martins@...cle.com>,
Venu Busireddy <venu.busireddy@...cle.com>,
vijay.balakrishna@...cle.com
Subject: Re: [virtio-dev] Re: [Qemu-devel] [PATCH] qemu: Introduce
VIRTIO_NET_F_STANDBY feature bit to virtio_net
On Fri, Jun 22, 2018 at 05:17:10PM -0700, Siwei Liu wrote:
> I forgot to mention the above has the assumption that we expose both
> STANDBY and UUID feature to QEMU user. In fact, as we're going towards
> not exposing the STANDBY feature directly to user, UUID may be always
> required to enable STANDBY.
Sounds good.
> If not, how do we make sure QEMU can
> control the visibility of primary device?
Hypervisors fundamentally always can control visibility of all
virtual devices.
> Something to be confirmed
> before implementing the code.
>
Powered by blists - more mailing lists