Messages in this thread | | | Date | Fri, 14 Apr 2006 00:49:12 +0200 (MEST) | From | Jan Engelhardt <> | Subject | Flexible mem= parameter |
| |
Hello,
mem= can be used to limit the amount of physical memory Linux uses. I presume that when specifying mem=256M only the memory from 0x0 to 0x10000000 is used. Is there a way to tune mem= so that it will use 0x70000000 to 0x80000000? (A compile-time change would suffice.)
Background: I am trying to track down a nondeterministic (but reproducible) segfault while building big projects like gcc or glibc. I do not think it's a memory problem since it only showed up since I changed to gcc 4.1.0 and tweaked it to use -mcpu=ultrasparc (rather than -mcpu=v7) by default. I had been building gcc4 before with gcc3 a number of times w/o problems. I did ran a userspace memtester for approx 20 hours (`memtest` from debian).
Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |