On Mon, Jan 28, 2013 at 5:09 PM, H. Peter Anvin <h...@zytor.com> wrote: > On 01/22/2013 07:20 AM, Thomas Renninger wrote: >> From: Yinghai Lu <ying...@kernel.org> >> >> memmap=exactmap will throw away all original, but also until then >> user defined (through other provided memmap= parameters) areas. >> That means all memmap= boot parameters passed before a memmap=exactmap >> parameter are not recognized. >> Without this fix: >> memmap=x@y memmap=exactmap memmap=i#k >> only i#k would get recognized. >> >> This is wrong, this fix will only throw away all original e820 areas once >> when memmap=exactmap is found in the whole boot command line and before >> any other memmap= option is parsed. >> > > I don't understand why this is wrong. The kernel command line is always > parsed from left to right, and I don't see anything inherently > problematic with that with something like a big hammer like exactmap.
Ok, let's drop it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
