From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Luis R. Rodriguez" Subject: Re: Xen's Linux kernel config options V2 Date: Thu, 5 Feb 2015 16:11:00 -0800 Message-ID: References: <54905BF1.2050608@suse.com> <20150109190200.GA4083@l.oracle.com> <54D1A70D.80906@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: 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: Juergen Gross Cc: "xen-devel@lists.xensource.com" , "Ian.Campbell@citrix.com" , Stefano Stabellini , David Vrabel , Jan Beulich , Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org On Thu, Feb 5, 2015 at 3:59 PM, Luis R. Rodriguez wrote: > On Tue, Feb 3, 2015 at 8:58 PM, Juergen Gross wrote: >> On 02/04/2015 01:48 AM, Luis R. Rodriguez wrote: >>>>> XEN_MAX_DOMAIN_MEMORY(x86) >>>> >>>> >>>> which depends on XEN_PV >>> >>> >>> Adjusted, but so far that's the only XEN_PV alone-dependent option. >>> Are you sure ? This defines MAX_DOMAIN_PAGES, and used on >>> arch/x86/xen/setup.c for xen_get_max_pages(). Can't this be used for >>> XEN_DOM0 ? >> >> >> This option will be replaced by another one once my patches for >> supporting >500GB pv-domains are ready. > > Great! > >> For now you could let it depend on XEN_HAVE_PVMMU. It is relevant for >> domUs as well. > > Well right now the only entity that selects XEN_HAVE_PVMMU is > CONFIG_XEN.. so that begs the question of which Kconfig options should > be selecting XEN_HAVE_PVMMU in the future? What about having it be > selected by XEN_BACKEND and also XEN_FRONTEND ? Nevermind I see you had it selected by XEN_PV(x86) already only, this would also satisfy Konrad's request to be able to build XEN_PVH without having to configure XEN_HAVE_PVMMU. Luis