[<prev] [next>] [day] [month] [year] [list]
Message-ID: <m1odnwpj6m.fsf@ebiederm.dsl.xmission.com>
Date: Wed, 14 Feb 2007 13:40:01 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Andi Kleen <ak@....de>, Andrew Morton <akpm@...l.org>,
virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com,
Chris Wright <chrisw@...s-sol.org>,
Ian Pratt <ian.pratt@...source.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [patch 21/21] Xen-paravirt: Add the Xen virtual network device driver.
Jeremy Fitzhardinge <jeremy@...p.org> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists