WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Shared memory and event channel

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Shared memory and event channel
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 23 Feb 2010 09:47:38 -0500
Cc: Ritu kaur <ritu.kaur.us@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Daniel Stodden <Daniel.Stodden@xxxxxxxxxx>
Delivery-date: Tue, 23 Feb 2010 07:22:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1266917906.11737.5928.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <29b32d341002211058l7e283336pa4fdfd0dc0b7124b@xxxxxxxxxxxxxx> <1266787199.24577.18.camel@xxxxxxxxxxxxxxxxxxxxxxx> <29b32d341002211533k4956a129ifff18281cfa92e41@xxxxxxxxxxxxxx> <1266825344.4996.183.camel@xxxxxxxxxxxxxxxxxxx> <29b32d341002220936q2f6f3cdaif3cbb766d1e644d1@xxxxxxxxxxxxxx> <1266874463.27288.57.camel@xxxxxxxxxxxxxxxxxxxxxxx> <29b32d341002221416t4e00b899q18e07a69ad24b07f@xxxxxxxxxxxxxx> <1266917906.11737.5928.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Tue, Feb 23, 2010 at 09:38:26AM +0000, Ian Campbell wrote:
> On Mon, 2010-02-22 at 22:16 +0000, Ritu kaur wrote:
> > 
> > All I need to  is access NIC registers via domU's(network controller
> > will still be working normally). Using PCI passthrough solves the
> > problem for a domU, however, it doesn't solve when multiple domU's
> > wanting to read NIC registers(ex. statistics).  
> 
> Direct access to hardware registers and availability of the device to
> multiple guest domains are mutually exclusive configurations under Xen
> (in the absence of additional technologies such as SR-IOV).
> 
> The paravirtual front and back devices contain no hardware specific
> functionality, in this configuration all hardware specific knowledge is
> contained in the driver in domain 0. Guests use regular L2 or L3
> mechanisms such as bridging, NAT or routing to obtain a path to the
> physical hardware but they are never aware of that physical hardware.
> 
> PCI passthrough allows a guest direct access to a PCI device but this is
> obviously incompatible with access from multiple guests (again, unless
> you have SR-IOV or something similar)

What if the netback was set be able to work in guest mode? This way you
could export it out to the guests?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel