summaryrefslogtreecommitdiffstats
path: root/bin/date
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>2003-10-04 06:30:56 +0000
committerpeter <peter@FreeBSD.org>2003-10-04 06:30:56 +0000
commitac3fcecc22637d0af58e2cafc2d51298ba5a3eca (patch)
treef7e428637f882658a4844d7067d99b9422ef1c48 /bin/date
parent9d93fce265aeeeb266999d5092d6d4224cc16829 (diff)
downloadFreeBSD-src-ac3fcecc22637d0af58e2cafc2d51298ba5a3eca.zip
FreeBSD-src-ac3fcecc22637d0af58e2cafc2d51298ba5a3eca.tar.gz
Emulate bugs in the old PSE code so that apm works again.
I do not yet understand why, but apm *depended* on the fact that the old PSE code caused the first 1MB of ram to be mapped read/write because it was in the same 4MB page as the kernel text+data+bss blob. If anybody ever tried DISABLE_PSE before, apm would not work. If your cpu did not have PSE, apm would not work there either (eg: 486). This bug has been around for a Very Long Time. The Pentium-4-fix commits did not emulate this unintended side effect of the PSE post-early-boot fixup, and thus apm blew up. I've added a hack to emulate the bug until either apm is fixed or we set fire to our bridges. This is bad though because it gives kernel mode code the opportunity to accidently write to the first few megs of the general page pool which is remapped at KERNBASE. It needs to be fixed properly.
Diffstat (limited to 'bin/date')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud