[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5087B13402000078000A3CBB@nat28.tlf.novell.com>
Date: Wed, 24 Oct 2012 08:13:24 +0100
From: "Jan Beulich" <JBeulich@...e.com>
To: "Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>,
<mukesh.rathor@...cle.com>
Cc: <Ian.Campbell@...rix.com>, <stefano.stabellini@...citrix.com>,
"xen-devel" <xen-devel@...ts.xen.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH V5] PVH patches for v3.8.
>>> On 23.10.12 at 20:12, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
Do you really want to target 3.8 for these, without any hypervisor
side review having happened? In particular,
> Changelog [since v4]
> - Mukesh addressed the reviewer's concerns.
> - Took Mukesh's patches and redid the changelogs.
> - Added Ack-ed as appropiate.
> - Fixed PVHVM 32-bit bootup issues.
> - Did some various cleanups, split some patches up.
>
> The big change is that I've made the xen_remove_from_physmap structure
> be of the same size and offset on 32 and 64 bit builds. Currently PVH
> only runs with 64-bit guests, but in the future it could run with 32-bit.
> This change will eliminate having to add a compat layer to deal with
> 32-bit hypercalls.
>
> Besides that the patches boot on an normal hypervisor - in
> dom0 (32 or 64bit), PV domU (32 or 64) and PVHVM domU (32 or 64).
> I don't have the PVH hypervisor patches so I could not address the
> change to xen_remove_from_physmap but I hope Mukesh can do that.
>
> The patches are also located at:
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/pvh.v5
>
>
> arch/x86/include/asm/xen/interface.h | 11 ++-
> arch/x86/include/asm/xen/page.h | 3 +
> arch/x86/xen/Kconfig | 10 ++
> arch/x86/xen/enlighten.c | 78 ++++++++++++----
> arch/x86/xen/irq.c | 5 +-
> arch/x86/xen/mmu.c | 162 ++++++++++++++++++++++++++++++++--
> arch/x86/xen/mmu.h | 2 +
> arch/x86/xen/p2m.c | 2 +-
> arch/x86/xen/setup.c | 58 +++++++++----
> arch/x86/xen/smp.c | 75 ++++++++++------
> arch/x86/xen/xen-head.S | 11 ++-
> drivers/xen/balloon.c | 15 ++--
> drivers/xen/cpu_hotplug.c | 4 +-
> drivers/xen/events.c | 9 ++-
> drivers/xen/gntdev.c | 3 +-
> drivers/xen/grant-table.c | 27 +++++-
> drivers/xen/privcmd.c | 72 ++++++++++++++-
> drivers/xen/xenbus/xenbus_client.c | 3 +-
> include/xen/interface/memory.h | 29 ++++++-
> include/xen/interface/physdev.h | 10 ++
... any changes to the hypervisor interface (didn't look in detail
what is being changed in these two headers) should first be in
at least -unstable before being consumed in any official release
imo.
Jan
> include/xen/xen-ops.h | 5 +-
> 21 files changed, 504 insertions(+), 90 deletions(-)
>
> Konrad Rzeszutek Wilk (4):
> xen/pvh: Fix PVHVM 32-bit bootup problems.
> xen/hypercall: Make xen_remove_from_physmap the same on 64/32 builds.
> xen/smp: Move the common CPU init code a bit to prep for PVH patch.
> xen/e820: Coalesce the PVH release/populate logic in the generic case.
>
> Mukesh Rathor (6):
> xen/pvh: Support ParaVirtualized Hardware extensions.
> xen/pvh: Extend vcpu_guest_context, p2m, event, and XenBus.
> xen/pvh: Implement MMU changes for PVH.
> xen/pvh: bootup and setup (E820) related changes.
> xen/pvh: balloon and grant changes.
> xen/pvh: /dev/xen/privcmd changes.
>
>
> _______________________________________________
> 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/
Powered by blists - more mailing lists