xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH for-4.5] libxl: don't use a qemu-ifup script on FreeBSD
Date: Mon, 29 Sep 2014 16:51:11 +0100	[thread overview]
Message-ID: <1412005871.3801.31.camel@citrix.com> (raw)
In-Reply-To: <54297E8D.50803@citrix.com>

On Mon, 2014-09-29 at 17:45 +0200, Roger Pau Monné wrote:
> El 29/09/14 a les 17.37, Ian Campbell ha escrit:
> > On Mon, 2014-09-29 at 16:05 +0200, Roger Pau Monné wrote:
> >> El 29/09/14 a les 15.35, Ian Campbell ha escrit:
> >>> On Fri, 2014-09-26 at 14:07 -0400, Konrad Rzeszutek Wilk wrote:
> >>>> On Fri, Sep 26, 2014 at 06:14:12PM +0200, Roger Pau Monne wrote:
> >>>>> FreeBSD doesn't use any qemu-ifup script in order to setup the network, it
> >>>>> is all done on the hotplug script like Linux.
> >>>>>
> >>>>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> >>>>> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> >>>>> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> >>>>> Cc: Ian Campbell <ian.campbell@citrix.com>
> >>>>> Cc: Wei Liu <wei.liu2@citrix.com>
> >>>>> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >>>>> ---
> >>>>> I request a code freeze exception on the basis that this is a bugfix and it
> >>>>> doesn't change the behaviour on platforms different than FreeBSD.
> >>>>
> >>>> <nods>
> >>>>
> >>>> Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >>>
> >>> Applied.
> >>>
> >>> I'm wondering if anyone should be using qemu-ifup these days?
> >>
> >> AFAIR, NetBSD uses it for qemu-trad at least. I was tempted to invert
> >> the ifdef and do something like:
> >>
> >> #ifdef __NetBSD__
> >> 	... use qemu-ifup
> >> #else
> >> 	... no ifup script
> >> #endif
> >>
> >> But I have no idea what Solaris does, or if we still try to support it.
> > 
> > Do we/libxl not call the scripts too in those cases?
> 
> Yes, the vif hotplug script is also called, but on NetBSD it just takes
> care of adding the vif, not the tap interface.
> 
> I think it's done this way on NetBSD because tap interfaces cannot be
> renamed, so only Qemu knows the actual unit/name of the tap interface
> and calls the qemu-ifup script passing that name as the first argument.

OK.



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-09-29 15:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 16:14 [PATCH for-4.5] libxl: don't use a qemu-ifup script on FreeBSD Roger Pau Monne
2014-09-26 18:07 ` Konrad Rzeszutek Wilk
2014-09-29 13:35   ` Ian Campbell
2014-09-29 14:05     ` Roger Pau Monné
2014-09-29 15:37       ` Ian Campbell
2014-09-29 15:45         ` Roger Pau Monné
2014-09-29 15:51           ` Ian Campbell [this message]
2014-09-29 10:13 ` Wei Liu

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=1412005871.3801.31.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).