From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
george.dunlap@eu.citrix.com, tim@xen.org,
ian.jackson@eu.citrix.com, linux-kernel@vger.kernel.org,
jbeulich@suse.com, xen-devel@lists.xenproject.org,
boris.ostrovsky@oracle.com
Subject: Re: [Xen-devel] [PATCH v10] Repost of PVH patches for Linux.
Date: Fri, 13 Dec 2013 09:30:39 -0500 [thread overview]
Message-ID: <20131213143039.GF2923@phenom.dumpdata.com> (raw)
In-Reply-To: <52AAF176.3020102@citrix.com>
On Fri, Dec 13, 2013 at 11:37:26AM +0000, David Vrabel wrote:
> On 13/12/13 02:10, Konrad Rzeszutek Wilk wrote:
> > Hey,
> >
> > Mukesh had posted them quite a while ago - they got reviewed, acked, etc,
> > put in #linux-next, got patches to fix some things from folks.
> >
> > Then everybody focused on the Xen patches .. and now that is mostly
> > baked this is what is needed on the Linux side to make it work
> > with PVH. I had them based on v3.6, then merged on v3.11, then..
> >
> > Decided to rebase all of them on v3.13-rc3 to make it easier.
>
> In general the series is a bit of mess, early patches doing things one
> way (using hypercalls that no longer exist for example) and later
> patches fixing things up. I think this should be sorted out as it makes
> it too difficult to review carefully (I've only given the series a
> quick, initial review).
I need from Mukesh the follow on patches that "fix" this
so I can rebase, squash, etc them them up a bit to make it easier.
>
> > Couple of things:
> >
> > a) the patch:
> > [PATCH V10 14/14] xen/pvh: vcpu info placement, load CS selector,
> >
> > could be split in three - and I think Mukesh did have a version like that.
> > I can do it myself and will - it should be obvious of how it will be done.
> >
> > b). Regression testing - I ran this with a Linux kernel dom0 (32 and 64)
> > on the latest Xen hypervisor without PVH enabled. It booted all the
> > guests I had:
> > RHEL5, SLES11, SLES12, F15, F16, F17, F18, F19, OEL5, OEL6, NetBSD PV,
> > FreeBSD HVM; and also 32 and 64 PV and PVHVM combination of the same
> > kernel (and save/restore on those). Nothing broke.
>
> That's good to know.
>
> David
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-12-13 14:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 2:10 [PATCH v10] Repost of PVH patches for Linux Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 01/14] xen/pvh: Support ParaVirtualized Hardware extensions Konrad Rzeszutek Wilk
2013-12-13 10:44 ` David Vrabel
2013-12-13 14:32 ` Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 02/14] xen/pvh: Extend vcpu_guest_context, p2m, event, and XenBus Konrad Rzeszutek Wilk
2013-12-13 10:56 ` David Vrabel
2013-12-13 14:26 ` Konrad Rzeszutek Wilk
2013-12-13 14:59 ` Stefano Stabellini
2013-12-13 2:10 ` [PATCH V10 03/14] xen/pvh: Implement MMU changes for PVH Konrad Rzeszutek Wilk
2013-12-13 16:54 ` Boris Ostrovsky
2013-12-13 2:10 ` [PATCH V10 04/14] xen/pvh: bootup and setup (E820) related changes Konrad Rzeszutek Wilk
2013-12-13 17:55 ` Boris Ostrovsky
2013-12-17 21:39 ` Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 05/14] xen/pvh: balloon and grant changes Konrad Rzeszutek Wilk
2013-12-13 11:02 ` David Vrabel
2013-12-13 11:56 ` Stefano Stabellini
2013-12-13 14:36 ` Konrad Rzeszutek Wilk
2013-12-13 14:49 ` Stefano Stabellini
2013-12-13 14:59 ` Konrad Rzeszutek Wilk
2013-12-13 15:34 ` Stefano Stabellini
2013-12-13 15:47 ` Konrad Rzeszutek Wilk
2013-12-13 15:51 ` Stefano Stabellini
2013-12-13 2:10 ` [PATCH V10 06/14] xen: x86 pvh: use XENMEM_add_to_physmap_range for foreign gmfn mappings Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 07/14] xen/x86: remove duplicated include from enlighten.c Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 08/14] x86/xen: Use __pa_symbol instead of __pa on C visible symbols Konrad Rzeszutek Wilk
2013-12-13 11:04 ` David Vrabel
2013-12-13 14:24 ` Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 09/14] xen: implement updated XENMEM_add_to_physmap_range ABI Konrad Rzeszutek Wilk
2013-12-13 11:35 ` David Vrabel
2013-12-13 14:27 ` Konrad Rzeszutek Wilk
2013-12-13 14:30 ` David Vrabel
2013-12-13 2:10 ` [PATCH V10 10/14] xen/pvh: specify xen features strings cleanly for PVH Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 11/14] xen/pvh: remove code to map iomem from guest Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 12/14] xen/pvh: Use ballooning to allocate grant table pages [v2] Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 13/14] x86/xen: remove depends on CONFIG_EXPERIMENTAL Konrad Rzeszutek Wilk
2013-12-13 2:10 ` [PATCH V10 14/14] xen/pvh: vcpu info placement, load CS selector, and remove debug printk Konrad Rzeszutek Wilk
2013-12-13 11:34 ` David Vrabel
2013-12-13 11:37 ` [PATCH v10] Repost of PVH patches for Linux David Vrabel
2013-12-13 14:30 ` Konrad Rzeszutek Wilk [this message]
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=20131213143039.GF2923@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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