| 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
| ||
|
Message-Id: <20110203122505.8369330f.akpm@linux-foundation.org> Date: Thu, 3 Feb 2011 12:25:05 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Yinghai Lu <yinghai@...nel.org> Cc: Ingo Molnar <mingo@...e.hu>, David Miller <davem@...emloft.net>, "H. Peter Anvin" <hpa@...or.com>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH - resend] memblock: Don't adjust size in memblock_find_base() On Fri, 28 Jan 2011 16:37:47 -0800 Yinghai Lu <yinghai@...nel.org> wrote: > > While applying patch to use memblock to find aperture for 64bit x86. > Ingo found system with 1g + force_iommu > > > No AGP bridge found > > Node 0: aperture @ 38000000 size 32 MB > > Aperture pointing to e820 RAM. Ignoring. > > Your BIOS doesn't leave a aperture memory hole > > Please enable the IOMMU option in the BIOS setup > > This costs you 64 MB of RAM > > Cannot allocate aperture memory hole (0,65536K) I'm trying to work out if we should backport this fix into earlier kernels and as is often the case, I wasn't given enough information. What are the end-user visible effects of this? The kernel cannot use the AGP bridge? 64MB of RAM wasted? Something else? -- 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