On Thu, Feb 5, 2015 at 3:59 PM, Luis R. Rodriguez <mcg...@do-not-panic.com> wrote: > On Tue, Feb 3, 2015 at 8:58 PM, Juergen Gross <jgr...@suse.com> 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
