From: Gerd Hoffmann <kraxel@suse.de>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: xen-devel@lists.xensource.com, xen-ia64-devel@lists.xensource.com
Subject: Re: [PATCH] new domain builder fix to boot domU on IA64.
Date: Wed, 31 Jan 2007 12:58:14 +0100 [thread overview]
Message-ID: <45C08456.4080903@suse.de> (raw)
In-Reply-To: <20070131025608.GE23281%yamahata@valinux.co.jp>
Isaku Yamahata wrote:
> XEN_DOMCTL_arch_setup hypercall sets up EFI memory map,
> xen-faked EFI firmware and etc. So it should be called before
> loading kernel/initrd images.
Why is this order important?
> How about adding new methods like setup_meminit, setup_firmware, setup_boot
> (Or please suggest better names.) to struct xc_dom_loader?
Certainly not to "struct xc_dom_loader", that one is for binary formats
such as ELF and thus architecture-independant.
Maybe we could put that into "struct xc_dom_arch". I've intentionally
tried to keep the code which does hypercalls separately though.
> And call setup_meminit at xc_dom_boot_mem_init(),
> setup_firmware at the beginning of xc_dom_build_image(),
> setup_boot at xc_dom_boot_image().
Only the xc_dom_boot_*() functions are supposed to invoke hypercalls.
Thus the firmware setup can happen either at the end of
xc_dom_boot_mem_init or at the start of xc_dom_boot_image.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
next prev parent reply other threads:[~2007-01-31 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 12:26 [PATCH] new domain builder fix to boot domU on IA64 Isaku Yamahata
2007-01-30 14:06 ` Gerd Hoffmann
2007-01-31 2:56 ` Isaku Yamahata
2007-01-31 11:58 ` Gerd Hoffmann [this message]
2007-02-01 2:57 ` [PATCH] new domain builder setup hook clean up (was Re: [PATCH] new domain builder fix to boot domU on IA64.) Isaku Yamahata
2007-02-01 7:59 ` Gerd Hoffmann
2007-02-01 11:40 ` Isaku Yamahata
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=45C08456.4080903@suse.de \
--to=kraxel@suse.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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.