From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Miller <davem@davemloft.net>
Cc: "jeremy@goop.org" <jeremy@goop.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"marmarek@invisiblethingslab.com"
<marmarek@invisiblethingslab.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen: do not disable netfront in dom0
Date: Tue, 22 May 2012 20:30:28 +0100 [thread overview]
Message-ID: <1337715028.3991.2.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <20120522.151354.2131168749992255398.davem@davemloft.net>
On Tue, 2012-05-22 at 20:13 +0100, David Miller wrote:
> From: Marek Marczykowski <marmarek@invisiblethingslab.com>
> Date: Sun, 20 May 2012 13:45:10 +0200
>
> > Netfront driver can be also useful in dom0, eg when all NICs are assigned to
> > some domU (aka driver domain). Then using netback in domU and netfront in dom0
> > is the only way to get network access in dom0.
> >
> > Signed-off-by: Marek Marczykowski <marmarek@invisiblethingslab.com>
>
> Someone please review this and I can merge it in via the 'net' tree if
> it looks OK to XEN folks.
Konrad is "Xen folks" and has acked it already but FWIW:
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-05-22 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 11:45 [PATCH] xen: do not disable netfront in dom0 Marek Marczykowski
2012-05-22 18:34 ` Konrad Rzeszutek Wilk
2012-05-22 19:13 ` David Miller
2012-05-22 19:30 ` Ian Campbell [this message]
2012-05-22 19:38 ` [Xen-devel] " David Miller
2012-05-22 19:43 ` Konrad Rzeszutek Wilk
2012-05-20 11:45 ` [PATCH RESENT] " Marek Marczykowski
2012-05-22 20:50 ` David Miller
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=1337715028.3991.2.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=davem@davemloft.net \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xen.org \
/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).