[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7ce41369-7784-862a-de8d-9cb2ecef83e1@oracle.com>
Date: Sun, 5 Mar 2017 12:59:08 -0500
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>,
xen-devel@...ts.xenproject.org
Cc: Juergen Gross <jgross@...e.com>, x86@...nel.org,
Andrew Jones <drjones@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [Xen-devel] [PATCH v2 00/21] x86/xen: untangle PV and PVHVM guest
support code
On 03/02/2017 12:53 PM, Vitaly Kuznetsov wrote:
> Changes since v1:
> - Patches 1,2 and 3 were split and reordered to avoid adding temporary
> #ifdefs [Juergen Gross]
> - Juergen's R-b added to what is now patches 14 and 15 (patches 4 and 5
> in v1). Due to re-ordering there are some tiny diffrences but I opted
> for keeping the tag.
>
> Some patches are known to produce checkpatch.pl WARNINGS and a couple of
> ERRORs, I fixed a few (mostly in _hvm* code I split) and I refrained from
> fixing the rest to make it easier to review. I think that we may leave PV
> code as it is as sooner or later it will go away.
>
> Original description:
>
> I have a long-standing idea to separate PV and PVHVM code in kernel and
> introduce Kconfig options to make it possible to enable the required
> parts only breaking the current 'all or nothing' approach.
I tried applying this to mainline and it failed at some point. Is there
a branch i can pull from?
Thanks.
-boris
Powered by blists - more mailing lists