All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [RFC v1 0/8] xen: kconfig changes
Date: Tue, 17 Feb 2015 08:26:26 +0100	[thread overview]
Message-ID: <54E2ED22.7080607@suse.com> (raw)
In-Reply-To: <CAB=NE6USqrRM2v2wns5JgY4sKZd3Y1W8EmnzwO+u=5MtQ2jabg@mail.gmail.com>

On 02/17/2015 01:25 AM, Luis R. Rodriguez wrote:
> On Mon, Feb 16, 2015 at 4:20 PM, Luis R. Rodriguez
> <mcgrof@do-not-panic.com> wrote:
>> As it is per our agreed upon changes we can in theory enable a
>> XEN_PVHVM system without XEN_PV or XEN_PVH. If this is indeed
>> desirable this poses an issue at build time
>
> And this also raises the question of whether or not we should make
> XEN_PVHVM a user selectable option, right now it is a def_bool and is
> therefore not human selectable. You can implicitly disable it by
> disabling PCI for example though. If we want that to be exposed to the
> user we can then enable some description of what that means, and the
> user will then be able to read / select / enable XEN_PV., XEN_PVHVM,
> XEN_PVH. Right now they'd only be able to select XEN_PV and/or
> XEN_PVH, XEN_PVHVM is implicit.

I think making XEN_PVHVM user selectable is okay.

Juergen

  reply	other threads:[~2015-02-17  7:26 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  6:03 [RFC v1 0/8] xen: kconfig changes Luis R. Rodriguez
2015-02-12  6:03 ` [RFC v1 1/8] xen: make dom0 specific changes depend on XEN_DOM0 Luis R. Rodriguez
2015-02-12  9:55   ` David Vrabel
2015-02-12 20:44     ` Luis R. Rodriguez
2015-02-12  6:03 ` [RFC v1 2/8] xen: x86: make XEN_MAX_DOMAIN_MEMORY depend on XEN_HAVE_PVMMU Luis R. Rodriguez
2015-02-12  9:56   ` David Vrabel
2015-02-12 20:45     ` Luis R. Rodriguez
2015-02-12  6:03 ` [RFC v1 3/8] xen: drivers: add XEN_FRONTEND and fold front end drivers under them Luis R. Rodriguez
2015-02-12 11:01   ` David Vrabel
2015-02-12 20:48     ` Luis R. Rodriguez
2015-02-12  6:03 ` [RFC v1 4/8] xen: x86: make XEN_PVH select XEN_PVHVM Luis R. Rodriguez
2015-02-25 15:44   ` Stefano Stabellini
2015-02-26  0:36     ` Luis R. Rodriguez
2015-02-12  6:03 ` [RFC v1 5/8] xen: x86: add XEN_PV Luis R. Rodriguez
2015-02-12 11:03   ` David Vrabel
2015-02-13  2:52     ` Luis R. Rodriguez
2015-02-12  6:03 ` [RFC v1 6/8] xen: x86: make XEN_PV* stuff depend on PARAVIRT and PARAVIRT_CLOCK Luis R. Rodriguez
2015-02-25 15:45   ` Stefano Stabellini
2015-02-26  0:54     ` Luis R. Rodriguez
2015-02-12  6:03 ` [RFC v1 7/8] xen: unwrap XEN_BACKEND from XEN_DOM0 Luis R. Rodriguez
2015-02-12 11:05   ` David Vrabel
2015-02-12 20:54     ` Luis R. Rodriguez
2015-02-25 14:17   ` Stefano Stabellini
2015-02-25 14:30     ` David Vrabel
2015-02-25 14:33       ` Stefano Stabellini
2015-02-26  1:08         ` Luis R. Rodriguez
2015-02-12  6:03 ` [RFC v1 8/8] xen: x86: remove CONFIG_XEN dependency PARAVIRT and PARAVIRT_CLOCK Luis R. Rodriguez
2015-02-12 11:07 ` [RFC v1 0/8] xen: kconfig changes David Vrabel
2015-02-17  0:20   ` Luis R. Rodriguez
2015-02-17  0:25     ` Luis R. Rodriguez
2015-02-17  7:26       ` Juergen Gross [this message]
2015-02-17 19:31         ` Luis R. Rodriguez
2015-02-18 18:11           ` Konrad Rzeszutek Wilk
2015-02-18 20:01             ` Luis R. Rodriguez
2015-02-18 20:20               ` Konrad Rzeszutek Wilk
2015-02-18 21:11                 ` Luis R. Rodriguez
2015-02-18 21:24                   ` Konrad Rzeszutek Wilk
2015-02-18 21:31                     ` Luis R. Rodriguez
2015-02-18 21:54                       ` Konrad Rzeszutek Wilk
2015-02-17  7:39     ` Juergen Gross
2015-02-17 20:12       ` Luis R. Rodriguez
2015-02-18  2:32         ` Luis R. Rodriguez
2015-02-18 10:03       ` David Vrabel
2015-02-18 10:12         ` Juergen Gross
2015-02-18 19:55           ` Luis R. Rodriguez
2015-02-20 13:55           ` David Vrabel
2015-02-20 16:04             ` Luis R. Rodriguez

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=54E2ED22.7080607@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=mcgrof@do-not-panic.com \
    --cc=mcgrof@suse.com \
    --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 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.