lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 19 Mar 2015 20:15:05 +0100 From: Paul Bolle <pebolle@...cali.nl> To: Juergen Gross <jgross@...e.com> Cc: linux-kernel@...r.kernel.org, xen-devel@...ts.xensource.com, konrad.wilk@...cle.com, david.vrabel@...rix.com, boris.ostrovsky@...cle.com, daniel.kiper@...cle.com Subject: Re: [PATCH 1/2] xen: prepare p2m list for memory hotplug On Thu, 2015-03-19 at 15:31 +0100, Juergen Gross wrote: > --- a/arch/x86/xen/p2m.c > +++ b/arch/x86/xen/p2m.c > +#ifdef CONFIG_X86_32 > +BUILD_BUG_ON_MSG(CONFIG_XEN_BALLOON_MEMORY_HOTPLUG_LIMIT > 64) > +#endif I assume BUILD_BUG_ON_MSG() aborts the build. > --- a/drivers/xen/Kconfig > +++ b/drivers/xen/Kconfig > +config XEN_BALLOON_MEMORY_HOTPLUG_LIMIT > + int > + default 512 if X86_64 > + default 4 if X86_32 > + depends on XEN_HAVE_PVMMU > + depends on XEN_BALLOON_MEMORY_HOTPLUG > + help > + Upper limit in GBs a pv domain can be expanded to using memory > + hotplug. > + > + This value is used to allocate enough space in internal tables needed > + for physical memory administration. > + I think adding a range 1 64 if X86_32 would allow to drop the BUILD_BUG_ON_MSG(). (I haven't tested this so you're allowed to bark at me if this ends up wasting your time.) Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists