From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] [PATCH] xen PVonHVM: require at least Xen 3.4 as dom0
Date: Wed, 31 Oct 2012 10:29:25 +0100 [thread overview]
Message-ID: <20121031092925.GA22587@aepfle.de> (raw)
In-Reply-To: <1351672212.20470.7.camel@hastur.hellion.org.uk>
On Wed, Oct 31, Ian Campbell wrote:
> If I understand correctly this requirements comes from the need to
> support moving the shared info page in order to support kexec?
>
> So could we do something more fine grained and limit only the kexec
> support (and therefore the movement of the SI into that range) to 3.4+?
Its not strictly about kexec. The other patch I sent out will place the
shared info page at 0xFE700000. If that range is not within a
E820_Reserved area and if the old hvmloader makes allocations within
that range, that other patch needs to be changed so that the shared info
page is done either at 0xFE700000 or within RESERVE_BRK (as it is done
currently).
Is the source code of that old RHEL available somewhere, did they patch
hvmloader at all? Providing a E820 map from a guest which was started on
such old dom0 would be a good start.
Olaf
next prev parent reply other threads:[~2012-10-31 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 16:05 [PATCH] xen PVonHVM: require at least Xen 3.4 as dom0 Olaf Hering
2012-10-30 18:17 ` Pasi Kärkkäinen
2012-10-30 18:28 ` [Xen-devel] " Olaf Hering
2012-10-31 8:30 ` Ian Campbell
2012-10-31 9:29 ` Olaf Hering [this message]
2012-10-31 10:21 ` Pasi Kärkkäinen
2012-10-31 11:48 ` Pasi Kärkkäinen
2012-10-31 10:25 ` Ian Campbell
2012-10-31 9:56 ` Olaf Hering
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=20121031092925.GA22587@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pasik@iki.fi \
--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 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).