The patch titled
fix x86_64-mm-early-param
has been added to the -mm tree. Its filename is
fix-x86_64-mm-early-param.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: fix x86_64-mm-early-param
From: Hugh Dickins <hugh@xxxxxxxxxxx>
I was impressed by how fast 2.6.18-rc3-mm2 is under memory pressure, until
I noticed that my "mem=512M" boot option was doing nothing. The two fixes
below got it working, but I wonder how many other early_param "option="
args are wrong (e.g. "memmap=" in the same file): x86_64 shows many such,
i386 shows only one, I've not followed it up further.
Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Cc: Andi Kleen <ak@xxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
arch/x86_64/kernel/e820.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/x86_64/kernel/e820.c~fix-x86_64-mm-early-param arch/x86_64/kernel/e820.c
--- a/arch/x86_64/kernel/e820.c~fix-x86_64-mm-early-param
+++ a/arch/x86_64/kernel/e820.c
@@ -598,11 +598,11 @@ static int __init parse_memopt(char *p)
{
if (!p)
return -EINVAL;
- end_user_pfn = memparse(p, NULL);
+ end_user_pfn = memparse(p, &p);
end_user_pfn >>= PAGE_SHIFT;
return 0;
}
-early_param("mem=", parse_memopt);
+early_param("mem", parse_memopt);
static int userdef __initdata;
_
Patches currently in -mm which might be from hugh@xxxxxxxxxxx are
git-agpgart.patch
fix-x86_64-mm-early-param.patch
mm-vm_bug_on.patch
mm-tracking-shared-dirty-pages.patch
mm-balance-dirty-pages.patch
mm-optimize-the-new-mprotect-code-a-bit.patch
mm-small-cleanup-of-install_page.patch
mm-fixup-do_wp_page.patch
mm-msync-cleanup.patch
mm-tracking-shared-dirty-pages-wimp.patch
mm-remove_mapping-safeness.patch
mm-remove_mapping-safeness-fix.patch
mm-swap-write-failure-fixup.patch
mm-swap-write-failure-fixup-fix.patch
make-prot_write-imply-prot_read.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
