From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-4502-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [66.179.20.138]) by lists.oasis-open.org (Postfix) with ESMTP id 9A43F1CB80F3 for ; Sat, 23 Jun 2018 18:45:51 -0700 (PDT) Date: Sun, 24 Jun 2018 04:45:36 +0300 From: "Michael S. Tsirkin" Message-ID: <20180624044436-mutt-send-email-mst@kernel.org> References: <20180621165913.7e3f4faa.cohuck@redhat.com> <20180622053141-mutt-send-email-mst@kernel.org> <20180623002628-mutt-send-email-mst@kernel.org> <20180623012406-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [virtio-dev] Re: [Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net To: Siwei Liu Cc: Cornelia Huck , "Samudrala, Sridhar" , Alexander Duyck , virtio-dev@lists.oasis-open.org, aaron.f.brown@intel.com, Jiri Pirko , Jakub Kicinski , Netdev , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, konrad.wilk@oracle.com, boris.ostrovsky@oracle.com, Joao Martins , Venu Busireddy , vijay.balakrishna@oracle.com List-ID: 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. > --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [virtio-dev] Re: [Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net Date: Sun, 24 Jun 2018 04:45:36 +0300 Message-ID: <20180624044436-mutt-send-email-mst@kernel.org> References: <20180621165913.7e3f4faa.cohuck@redhat.com> <20180622053141-mutt-send-email-mst@kernel.org> <20180623002628-mutt-send-email-mst@kernel.org> <20180623012406-mutt-send-email-mst@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Siwei Liu Cc: Alexander Duyck , virtio-dev@lists.oasis-open.org, Jiri Pirko , konrad.wilk@oracle.com, Jakub Kicinski , "Samudrala, Sridhar" , Cornelia Huck , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Venu Busireddy , Netdev , boris.ostrovsky@oracle.com, aaron.f.brown@intel.com, Joao Martins List-Id: virtualization@lists.linuxfoundation.org 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. >