| 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: Tue, 6 Feb 2007 17:16:24 +0100 From: "Andreas Herrmann" <andreas.herrmann3@....com> To: "Jan Beulich" <jbeulich@...ell.com> cc: "Andi Kleen" <ak@...e.de>, "Suresh B Siddha" <suresh.b.siddha@...el.com>, "Richard Gooch" <rgooch@...e-mbox.com>, linux-kernel@...r.kernel.org, discuss@...-64.org Subject: Re: [discuss] [patch] mtrr: fix issues with large addresses On Tue, Feb 06, 2007 at 09:31:45AM +0000, Jan Beulich wrote: > >>> Andi Kleen <ak@...e.de> 06.02.07 08:53 >>> > >On Monday 05 February 2007 23:50, Siddha, Suresh B wrote: > >> On Mon, Feb 05, 2007 at 06:19:59PM +0100, Andreas Herrmann wrote: > >> > o added check to restrict base address to 36 bit on i386 > >> > >> Why is this? It can go upto implemented physical bits, right? > > > >In theory it can, but Linux doesn't support it. > > I don't think I remember a restriction here, at least not below 44 bits > (that's where pfn-s would need to become 64-bit wide). > > Jan > Hi all, shame on me. Wanted to fix and interface issue where base address is truncated at 44 bit in mtrr_write(). (And just thought 36 bit would be more than enough for that 32 bit Linux version :) Regards, Andreas -- AMD Saxony, Dresden, Germany Operating System Research Center - 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