From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [RFC v1 0/8] xen: kconfig changes
Date: Wed, 18 Feb 2015 15:20:54 -0500
Message-ID: <20150218202054.GA19571@l.oracle.com>
References: <1423720996-3332-1-git-send-email-mcgrof@do-not-panic.com>
	<54DC8974.5060908@citrix.com>
	<CAB=NE6XJfYVbso20sBPN08dhQDneg3R9xtUWxFRC5gmTtRRoAQ@mail.gmail.com>
	<CAB=NE6USqrRM2v2wns5JgY4sKZd3Y1W8EmnzwO+u=5MtQ2jabg@mail.gmail.com>
	<54E2ED22.7080607@suse.com>
	<CAB=NE6W+y3upr_u1GTzrtARkf7bbTU+Eaorq22rWue3DpehiPw@mail.gmail.com>
	<20150218181120.GL8152@l.oracle.com>
	<CAB=NE6VSYW8pAAYn2ayh5onJaPb1-Js+eFnFsuBR3WjeyGt3-A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <konrad.wilk@oracle.com>) id 1YOB7I-0003Jw-2a
	for xen-devel@lists.xenproject.org; Wed, 18 Feb 2015 20:21:04 +0000
Content-Disposition: inline
In-Reply-To: <CAB=NE6VSYW8pAAYn2ayh5onJaPb1-Js+eFnFsuBR3WjeyGt3-A@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org, Boris Ostrovsky <boris.ostrovsky@oracle.com>, David Vrabel <david.vrabel@citrix.com>, "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, Feb 18, 2015 at 12:01:43PM -0800, Luis R. Rodriguez wrote:
> On Wed, Feb 18, 2015 at 10:11 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Tue, Feb 17, 2015 at 11:31:08AM -0800, Luis R. Rodriguez wrote:
> >> On Mon, Feb 16, 2015 at 11:26 PM, Juergen Gross <jgross@suse.com> wrote:
> >> > 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.
> >>
> >> OK I'll enable this then.
> >
> > Please don't. We had bugs in the past because distros did not select
> > it (they made it an module) and the PV drivers were not loaded.
> 
> Oy vey.
> 
> > There should be an history in the git tree behind the desire to make
> > it non selectable.
> 
> OK how about we enable the user selection only under CONFIG_EXPERT,
> otherwise make it hidden.

The CONFIG_EXPERT is gone from the kernel..
> 
>  Luis