Searched hist:"1 c675a3bc30cd3c5fb7973c8444ae662c52df4fe" (Results 1 – 2 of 2) sorted by relevance
| /freebsd/sys/conf/ |
| H A D | ldscript.amd64 | diff 1c675a3bc30cd3c5fb7973c8444ae662c52df4fe Mon Mar 28 08:35:17 CEST 2011 Alan Cox <alc@FreeBSD.org> The new binutils has correctly redefined MAXPAGESIZE on amd64 as 0x200000
instead of 0x100000. As a side effect, an amd64 kernel now loads at
physical address 0x200000 instead of 0x100000. This is probably for the
best because it avoids the use of a 2MB page mapping for the first 1MB of
the kernel that also spans the fixed MTRRs. However, getmemsize() still
thinks that the kernel loads at 0x100000, and so the physical memory between
0x100000 and 0x200000 is lost. Fix this problem by replacing the hard-wired
constant in getmemsize() by a symbol "kernphys" that is defined by the
linker script.
In collaboration with: kib
|
| /freebsd/sys/amd64/amd64/ |
| H A D | machdep.c | diff 1c675a3bc30cd3c5fb7973c8444ae662c52df4fe Mon Mar 28 08:35:17 CEST 2011 Alan Cox <alc@FreeBSD.org> The new binutils has correctly redefined MAXPAGESIZE on amd64 as 0x200000
instead of 0x100000. As a side effect, an amd64 kernel now loads at
physical address 0x200000 instead of 0x100000. This is probably for the
best because it avoids the use of a 2MB page mapping for the first 1MB of
the kernel that also spans the fixed MTRRs. However, getmemsize() still
thinks that the kernel loads at 0x100000, and so the physical memory between
0x100000 and 0x200000 is lost. Fix this problem by replacing the hard-wired
constant in getmemsize() by a symbol "kernphys" that is defined by the
linker script.
In collaboration with: kib
|