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, 15 Oct 2020 09:17:12 -0400 From: boris.ostrovsky@...cle.com To: Andrew Cooper <andrew.cooper3@...rix.com>, Jason Andryuk <jandryuk@...il.com>, Juergen Gross <jgross@...e.com>, Stefano Stabellini <sstabellini@...nel.org> Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>, xen-devel@...ts.xenproject.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] xen: Kconfig: nest Xen guest options On 10/15/20 9:10 AM, Andrew Cooper wrote: > On 15/10/2020 13:37, boris.ostrovsky@...cle.com wrote: >> On 10/14/20 1:53 PM, Jason Andryuk wrote: >>> +config XEN_512GB >>> + bool "Limit Xen pv-domain memory to 512GB" >>> + depends on XEN_PV && X86_64 >> Why is X86_64 needed here? >> 512G support was implemented using a direct-mapped P2M, and is rather > beyond the virtual address capabilities of 32bit. > Yes, my point was that XEN_PV already depends on X86_64. -boris
Powered by blists - more mailing lists