xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Juergen Gross <jgross@suse.com>,
	xen-devel@lists.xenproject.org, Andrew Jones <drjones@redhat.com>,
	x86@kernel.org, David Vrabel <david.vrabel@citrix.com>
Subject: Re: [RFC PATCH KERNEL 0/4] x86/xen: untangle PV and PVHVM guest support code
Date: Tue, 15 Nov 2016 12:14:49 +0100	[thread overview]
Message-ID: <87y40l6lli.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <11845813-3eaf-5c52-9170-81855c733ef5@oracle.com> (Boris Ostrovsky's message of "Mon, 14 Nov 2016 13:47:39 -0500")

Boris Ostrovsky <boris.ostrovsky@oracle.com> writes:

> On 11/14/2016 01:21 PM, David Vrabel wrote:
>> On 14/11/16 17:17, Vitaly Kuznetsov wrote:
>>> Hi,
>>>
>>> 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.
>>>
>>> Motivation:
>>> - Xen related x86 code in kernel is rather big and it is unclear which
>>>   parts of it are required for PV, for HVM or for both. With PVH coming
>>>   into picture is becomes even more tangled. It makes it hard to
>>>   understand/audit the code.
>>>
>>> - In some case we may want to avoid bloating kernel by supporting Xen
>>>   guests we don't need. In particular, 90% of the code in arch/x86/xen/ is
>>>   required to support PV guests and one may require PVHVM support only.
>>>
>>> - PV guests are supposed to go away one day and such code separation would
>>>   help us to get ready.
>> All good reasons.

Good, let's do it then)

>>> This RFC adds XEN_PV Kconfig option and makes it possible to build PV-only
>>> and PVHVM-only kernels. It also makes it possible to disable Dom0 support.
>>> The series is incomplete and probably dirty in some places, I didn't pay
>>> much attention to the current PVH implementation as (as far as I
>>> understand) it is supposed to be replaced with PVHv2 but before investing
>>> more I'd like to get opinions whether such refactoring will be welcomed.
>> This series might be best done after PVHv1 is removed.  Boris, any
>> thoughts on the best approach here?
>
> I would prefer to wait until at least domU PVHv2 (together with removal
> of v1) happens. As soon as I am done with ACPI hotplug on the hypervisor
> side I will post the new version.

Sure, there is no rush here.

-- 
  Vitaly

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-11-15 11:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 17:17 [RFC PATCH KERNEL 0/4] x86/xen: untangle PV and PVHVM guest support code Vitaly Kuznetsov
2016-11-14 17:17 ` [RFC PATCH KERNEL 1/4] x86/xen: start untangling " Vitaly Kuznetsov
2016-11-15 11:26   ` David Vrabel
2016-11-15 12:08     ` Vitaly Kuznetsov
2016-11-15 15:50   ` Boris Ostrovsky
2016-11-14 17:17 ` [RFC PATCH KERNEL 2/4] x86/xen: split smp.c for PV and PVHVM guests Vitaly Kuznetsov
2016-11-14 17:17 ` [RFC PATCH KERNEL 3/4] x86/xen: put setup.c, mmu.c and p2m.c under CONFIG_XEN_PV Vitaly Kuznetsov
2016-11-14 17:17 ` [RFC PATCH KERNEL 4/4] x86/xen: put setup.c, pmu.c and apic.c " Vitaly Kuznetsov
2016-11-14 18:21 ` [RFC PATCH KERNEL 0/4] x86/xen: untangle PV and PVHVM guest support code David Vrabel
2016-11-14 18:47   ` Boris Ostrovsky
2016-11-15 11:14     ` Vitaly Kuznetsov [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=87y40l6lli.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=drjones@redhat.com \
    --cc=jgross@suse.com \
    --cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).