|  |  | 
  
    |  |  | 
 
  |   |  | 
  
    |  |  | 
  
    |  |  | 
  
    |   xen-devel
[Xen-devel] Re: [patch 21/21] Xen-paravirt: Add the Xen virtual	network  
| To: | Jeremy Fitzhardinge <jeremy@xxxxxxxx> |  
| Subject: | [Xen-devel] Re: [patch 21/21] Xen-paravirt: Add the Xen virtual	network device driver. |  
| From: | ebiederm@xxxxxxxxxxxx (Eric W. Biederman) |  
| Date: | Wed, 14 Feb 2007 13:40:01 -0700 |  
| Cc: | Andrew Morton <akpm@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx,	Ian Pratt <ian.pratt@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxxxxxx,	linux-kernel@xxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxxxxxx>,	Andi Kleen <ak@xxxxxx>, virtualization@xxxxxxxxxxxxxx |  
| Delivery-date: | Thu, 15 Feb 2007 01:39:55 -0800 |  
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |  
| In-reply-to: | <20070213221831.150207238@xxxxxxxx> (Jeremy Fitzhardinge's	message of "Tue, 13 Feb 2007 14:17:50 -0800") |  
| 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/cgi-bin/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |  
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |  
| References: | <20070213221729.772002682@xxxxxxxx>	<20070213221831.150207238@xxxxxxxx> |  
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |  
| User-agent: | Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) |  
| Jeremy Fitzhardinge <jeremy@xxxxxxxx> writes:
> +++ b/drivers/xen/Kconfig.net
> @@ -0,0 +1,14 @@
> +menu "Xen network device drivers"
> +        depends on NETDEVICES && XEN
> +
> +config XEN_NETDEV_FRONTEND
> +     tristate "Network-device frontend driver"
> +     depends on XEN
> +     default y
> +     help
> +       The network-device frontend driver allows the kernel to access
> +       network interfaces within another guest OS. Unless you are building a
> +       dedicated device-driver domain, or your master control domain
> +       (domain 0), then you almost certainly want to say Y here.
Am I reading this correctly I can directly use the network interface
of another guest OS (no protection)?
I think this description is misleading, and probably say something
about virtual hardware.
Eric
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 | 
 |  | 
  
    |  |  |