From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
xen-devel@lists.xensource.com, Chris Wright <chrisw@sous-sol.org>,
Ian Pratt <ian.pratt@xensource.com>,
virtualization@lists.osdl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 21/21] Xen-paravirt: Add the Xen virtual network device driver.
Date: Wed, 14 Feb 2007 13:40:01 -0700 [thread overview]
Message-ID: <m1odnwpj6m.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070213221831.150207238@goop.org> (Jeremy Fitzhardinge's message of "Tue, 13 Feb 2007 14:17:50 -0800")
Jeremy Fitzhardinge <jeremy@goop.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
next prev parent reply other threads:[~2007-02-14 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070213221729.772002682@goop.org>
2007-02-13 22:17 ` [patch 21/21] Xen-paravirt: Add the Xen virtual network device driver Jeremy Fitzhardinge
2007-02-14 20:40 ` Eric W. Biederman [this message]
[not found] <20070216022449.739760547@goop.org>
2007-02-16 2:25 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1odnwpj6m.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=ian.pratt@xensource.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).