From: Olaf Hering <olaf@aepfle.de>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen PVonHVM: require at least Xen 3.4 as dom0
Date: Tue, 30 Oct 2012 19:28:59 +0100 [thread overview]
Message-ID: <20121030182859.GA8775@aepfle.de> (raw)
In-Reply-To: <20121030181732.GZ8912@reaktio.net>
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@aepfle.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.
Olaf
next prev parent reply other threads:[~2012-10-30 18:29 UTC|newest]
Thread overview: 10+ 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 ` [Xen-devel] " Pasi Kärkkäinen
2012-10-30 18:17 ` Pasi Kärkkäinen
2012-10-30 18:28 ` Olaf Hering [this message]
2012-10-31 8:30 ` [Xen-devel] " Ian Campbell
2012-10-31 9:29 ` Olaf Hering
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=20121030182859.GA8775@aepfle.de \
--to=olaf@aepfle.de \
--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 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.