From: Gerd Hoffmann <kraxel@suse.de>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: bimodal PAE and compatibility
Date: Mon, 08 Jan 2007 16:24:04 +0100 [thread overview]
Message-ID: <45A26214.8040300@suse.de> (raw)
In-Reply-To: <20070108151609.GD1557@totally.trollied.org.uk>
John Levon wrote:
> On Mon, Jan 08, 2007 at 04:05:36PM +0100, Gerd Hoffmann wrote:
>
>>> We currently ship a PAE 32-bit domU that we can trivially make bimodal,
>>> except that if we set it to "bimodal", then older Xens will default to
>>> thinking the domU is not PAE:
>>>
>>> 353 dsi->pae_kernel = PAEKERN_no;
>>> 354 if ( dsi->__elfnote_section )
>>> 355 {
>>> 356 p = xen_elfnote_string(dsi, XEN_ELFNOTE_PAE_MODE);
>>> 357 if ( p != NULL && strncmp(p, "yes", 3) == 0 )
>>> 358 dsi->pae_kernel = PAEKERN_extended_cr3;
>>>
>>> Could we have a new note instead?
>> I don't think it improves the situation, for older Xens you need two
>> kernels anyway, even if the only difference is the content of the
>> pae_mode elf note ...
>
> What do you mean? Are you saying that Xen complains about an ELF note it
> doesn't understand?
No.
Moving the bimodal flag to another elf node doesn't fix the problem that
older Xen versions don't support bimodal kernels, thus you still need a
pae and a non-pae kernel. As older Xens consider bimodal kernels as
non-pae one bimodal and one pae kernel works too. But you can't get
that down to only one kernel unless you drop support for xen versions
below 3.0.4 ...
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
next prev parent reply other threads:[~2007-01-08 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 14:49 bimodal PAE and compatibility John Levon
2007-01-08 15:05 ` Gerd Hoffmann
2007-01-08 15:16 ` John Levon
2007-01-08 15:24 ` Gerd Hoffmann [this message]
2007-01-08 15:29 ` John Levon
2007-01-08 16:52 ` Gerd Hoffmann
2007-01-08 16:24 ` Keir Fraser
2007-01-08 17:27 ` John Levon
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=45A26214.8040300@suse.de \
--to=kraxel@suse.de \
--cc=levon@movementarian.org \
--cc=xen-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.