From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-ppc-devel <xen-ppc-devel@lists.xensource.com>,
Xen Development Mailing List <xen-devel@lists.xensource.com>,
Hollis Blanchard <hollisb@us.ibm.com>,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: New domain builder in xen-unstable
Date: Mon, 29 Jan 2007 14:20:54 +0100 [thread overview]
Message-ID: <45BDF4B6.7040402@suse.de> (raw)
In-Reply-To: <C1DFE623.7E06%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 26/1/07 5:04 pm, "Hollis Blanchard" <hollisb@us.ibm.com> wrote:
>
>>> Not sure what you mean by "our own domain builder"; we've been
>>> implementing xc_linux_build() for quite a while now (and thus integrated
>>> with xend).
>> Sorry, I misunderstood. I was seeing all the libelf churn, and I missed
>> the fact that xc_linux_build() is going away entirely (?).
>>
>> I'm still not sure what you mean by "our own domain builder" -- there is
>> simply no way we're going to add more ifdefs to
>> tools/libxc/xc_linux_build.c (or equivalent)...
>
> 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.
libelf is used both within the xen kernel (dom0 builder) and the tools.
Have a look at changeset 13618, this does the dom0 builder port for x86
and ia64 (build-tested only), something simliar is needed for the ppc
dom0 builder.
For the tools: You can either switch over the existing ppc builder in
libxc/powerpc/ to use libelf, which likely is simliar to the dom0
builder conversion to libelf.
The other option is to use the new builder code in libxc/xc_dom_*.c.
Some code is already there. The ia64 bits should at least compile, with
luck even work out-of-the-box. The ppc bits I didn't even compile. The
places with architecture-specific code are:
xc_dom_{ia64,powerpc}.c
setup arch-specific structs (start_info, vcpu_context).
xc_dom_boot.c
invoke the hypercalls needed to boot the domain. There are two
functions for architecture-specific code, ppc must hook in the
devtree setup there (if you decide to use the new builder).
The domain builder core code should need no changes in theory ;)
Feel free to ask if there are any questions.
HTH & cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
next prev parent reply other threads:[~2007-01-29 13:20 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 [this message]
2007-03-06 20:56 ` Hollis Blanchard
2007-03-07 0:59 ` [XenPPC] " Brendan Cully
2007-03-07 8:27 ` 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=45BDF4B6.7040402@suse.de \
--to=kraxel@suse.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=hollisb@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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.