[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1351679139.25014.10.camel@hastur.hellion.org.uk>
Date: Wed, 31 Oct 2012 11:25:39 +0100
From: Ian Campbell <ian.campbell@...rix.com>
To: Olaf Hering <olaf@...fle.de>
CC: Pasi Kärkkäinen <pasik@....fi>,
Jeremy Fitzhardinge <jeremy@...p.org>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: [Xen-devel] [PATCH] xen PVonHVM: require at least Xen 3.4 as
dom0
On Wed, 2012-10-31 at 09:29 +0000, Olaf Hering wrote:
> 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.
Right, but it does this only in order to support kexec, right? Is there
any other reason to relocate the shinfo in this way?
> 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).
Can it not do both, depending on the detected version of Xen? That's
what I was trying to suggest.
> 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.
IIRC The .src.rpm's are available on ftp.redhat.com, or you could
probaly find the centos versions.
Ian.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists