linux-kernel - Re: [Xen-devel] [PATCH] xen PVonHVM: require at least Xen 3.4 as dom0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1351672212.20470.7.camel@hastur.hellion.org.uk>
Date:	Wed, 31 Oct 2012 09:30:12 +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 Tue, 2012-10-30 at 18:28 +0000, Olaf Hering wrote:
> On Tue, Oct 30, Pasi Kärkkäinen wrote:
> 
> > On Tue, Oct 30, 2012 at 05:05:05PM +0100, Olaf Hering wrote:
> > > The XenPVHVM extensions have not been tested much on very old
> > > hypervisors. At least Xen 3.4 gets some testing with the pvops kernel.
> > > 
> > > Require at least Xen 3.4 for the PVonHVM extensions. If an older
> > > hypervisor is detected the extensions will be disabled and the guest
> > > will only see emulated hardware.
> > > 
> > > Signed-off-by: Olaf Hering <olaf@...fle.de>
> > >
> > 
> > IIRC upstream Linux PVonHVM drivers do work OK today on RHEL5 Xen, 
> > which advertises itself as Xen 3.1.2-based..
> 
> If thats the case, and a combination thats supposed to work, the patch
> can be dropped if the hvmloader does really leave room at
> FE700000-FE800000.

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+?

Ian.

> 
> Olaf
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@...ts.xen.org
> http://lists.xen.org/xen-devel


--
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/