| 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, 4 Mar 2008 17:47:32 +0100 From: Ingo Molnar <mingo@...e.hu> To: "H. Peter Anvin" <hpa@...or.com> Cc: Rick van Rein <rick@...rein.org>, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory * H. Peter Anvin <hpa@...or.com> wrote: >>>> >>> How is this different from: >>> >>> memmap=<size>$<len> >>> >>> ... ? >> >> it's the inverse? When we identify bad areas of RAM, we really want to >> "punch holes" into the existing memory map. So 'badram=' or 'excludemem=' >> would be nicer and easier to use. >> >> Or extend 'memmap=' with an inverse parameter: memmap=!0x10000000$1M would >> exclude a 1MB region at 256MB physical. >> > > My understanding is that the $-form (as opposed to the @-form or > #-form) is exactly that: > > memmap=nn[KMG]$ss[KMG] > [KNL,ACPI] Mark specific memory as reserved. > Region of memory to be used, from ss to ss+nn. > > "Reserved" usually means "don't use as either memory or free address > space". ah - thanks - didnt know that! i guess there might still be badram syntax details that might be worth merging, but "memmap=" looks a lot more complete than what i thought it to be. Ingo -- 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