From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [RFC v1 0/8] xen: kconfig changes Date: Tue, 17 Feb 2015 08:26:26 +0100 Message-ID: <54E2ED22.7080607@suse.com> References: <1423720996-3332-1-git-send-email-mcgrof@do-not-panic.com> <54DC8974.5060908@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNcYC-0003gn-CZ for xen-devel@lists.xenproject.org; Tue, 17 Feb 2015 07:26:32 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Luis R. Rodriguez" , David Vrabel , Konrad Rzeszutek Wilk Cc: xen-devel@lists.xenproject.org, Boris Ostrovsky , "Luis R. Rodriguez" List-Id: xen-devel@lists.xenproject.org On 02/17/2015 01:25 AM, Luis R. Rodriguez wrote: > On Mon, Feb 16, 2015 at 4:20 PM, Luis R. Rodriguez > 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