Prev: [PATCH v2] regulator: new drivers for AD5398 and AD5821
Next: block: push down BKL into .locked_ioctl
From: Maxim Levitsky on 2 Jun 2010 06:20 Hi, I need to reserve a region of ram to store there a ramoops buffer. I need to do so early so kernel doesn't overwrite the existing contents. How to do it? I noticed that doing memmap=20M$0x70000000 crashes the system although it promised to work. Is that a bug? I have 2GB system with following memory map: [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) [ 0.000000] BIOS-e820: 0000000000100000 - 000000007fcfd000 (usable) [ 0.000000] BIOS-e820: 000000007fcfd000 - 000000007fd08000 (reserved) [ 0.000000] BIOS-e820: 000000007fd08000 - 000000007fd52000 (usable) [ 0.000000] BIOS-e820: 000000007fd52000 - 000000007fd55000 (reserved) [ 0.000000] BIOS-e820: 000000007fd55000 - 000000007fdbb000 (usable) [ 0.000000] BIOS-e820: 000000007fdbb000 - 000000007fdbf000 (reserved) [ 0.000000] BIOS-e820: 000000007fdbf000 - 000000007fe70000 (usable) [ 0.000000] BIOS-e820: 000000007fe70000 - 000000007febf000 (ACPI NVS) [ 0.000000] BIOS-e820: 000000007febf000 - 000000007ff00000 (ACPI data) [ 0.000000] BIOS-e820: 000000007ff00000 - 0000000080000000 (reserved) [ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) [ 0.000000] BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved) [ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved) [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) Best regards, Maxim Levitsky -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |