From: Brendan Cully <brendan@cs.ubc.ca>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>,
Gerd Hoffmann <kraxel@suse.de>,
xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: [XenPPC] Re: New domain builder in xen-unstable
Date: Tue, 6 Mar 2007 16:59:28 -0800 [thread overview]
Message-ID: <20070307005928.GD4424@ventoux.cs.ubc.ca> (raw)
In-Reply-To: <1173214613.12803.21.camel@basalt>
On Tuesday, 06 March 2007 at 14:56, Hollis Blanchard wrote:
> On Fri, 2007-01-26 at 17:08 +0000, Keir Fraser wrote:
> > xc_linux_build() is still provided in the 'new world' and is still
> > used by xend. For ia64/x86 it is now a thin wrapper around Gerd's new
> > domain-building infrastructure. For ppc you can continue to have your
> > very own version under libxc/powerpc if you want to, and not use
> > Gerd's new domain-building infrastructure. But the elf code that you
> > rely on is going away, so you need to move to using libelf, which I'm
> > sure Gerd can give you some pointers about.
>
> Hi Keir, it turns out I was confused about libxc, and we were depending
> on the just-removed ELF loader. I'm fixing that now; please give me a
> heads-up on the 3.0.5 release so I'm not caught out.
>
> Aside from that, it seems that xc_linux_build() is actually not called
> by anybody any longer. It looks like changeset a20ec270998b (from
> Brendan) removed the call from xc.c, replacing it with a call to the
> "new style" domain builder via xc_dom_linux_build().
>
> The new domain builder infrastructure is not flexible enough for
> PowerPC, so we're sticking with our own xc_linux_build(). It sounded
> before like that would be possible, so I assume a20ec270998b was just an
> oversight?
I have to admit, I haven't really looked at how other architectures
are overriding the domain building stuff. Would it be possible to
override xc_dom_linux_build to grab the couple of extra parameters
you need (cmdline, features) from dom and pass them to your existing
xc_linux_build? Then you can pass back elfnotes to python at your
convenience, if/when it makes sense.
next prev parent reply other threads:[~2007-03-07 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 13:43 New domain builder in xen-unstable Keir Fraser
2007-01-26 16:58 ` Hollis Blanchard
2007-01-26 17:04 ` Hollis Blanchard
2007-01-26 17:08 ` Keir Fraser
2007-01-29 13:20 ` Gerd Hoffmann
2007-03-06 20:56 ` Hollis Blanchard
2007-03-07 0:59 ` Brendan Cully [this message]
2007-03-07 8:27 ` [XenPPC] " Keir Fraser
2007-03-09 22:05 ` Hollis Blanchard
2007-03-15 9:54 ` Gerd Hoffmann
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=20070307005928.GD4424@ventoux.cs.ubc.ca \
--to=brendan@cs.ubc.ca \
--cc=hollisb@us.ibm.com \
--cc=kraxel@suse.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ppc-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.