Robert Hancock wrote:
I think that mem=8832M would work as well, to make the kernel use only
the memory that is marked cacheable. (It looks like this parameter
takes the highest memory address we want the kernel to use, not the
highest memory amount.)
Yep, and that would be much easier too.
I am curious though as this seems to be somewhat common a problem, could
we make the kernel analyze which memory is not cacheable (it already
knows this via MTRR) and not use that portion for anything? Plus may be
warn the user to contact their BIOS vendor to correct the problem?
I think that would be possible - even if the kernel knows late that the
memory was uncached we could migrate those pages in that region to
someplace else?
Parag
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
