Only assembly version for i386 bswap16 and bswap32 for now (bswap64 uses
bswap32). Contribution of assembly versions of these are welcome.
Add byte-swapping of ext2fs metadata for big-endian systems.
Tested on i386 and sparc.
of the reserved KVAs (vpage[]) used by these routines. This avoids the
context switching in there.
* In pmap_redzone(), remove the first kernel address (at KERNBASE) from
the kernel maps instead of just turning off the PTE `valid' bits.
The latter doesn't create a "red zone" at all, but causes the VM to
allocate a new page if the red zone is touched.
uncached (if needed) chunks of memory of the two sizes (256 and 1024
bytes) that the SRMMU ever needs.
* Change pmap_changeprot4m() so that is does not rely setpte4m() because
setpte4m() cannot be used for anything other than VAs that are in the
pmap associated with the current context.
In the same vain, make sure that kvm_uncache() switches to context 0.
don't buck the trend and move the call to initmsgbuf() to cpu_startup()
in machdep.c (like most other ports do) where we can setup things right
in one go. (This means that the CSRG copyright will no longer be in
the kernel logs).
msgbuf. Note that old 'dmesg' and 'syslogd' binaries will continue running,
though old 'dmesg' binaries will output a few bytes of junk at the start of
the buffer, and will miss a few bytes at the end of the buffer.
set on viking MXCC machines while using transparent memory access mode. This
becomes apparent when booting on multi-processor viking machines.
While I'm here, arrange to tempt fate a little less by using `AC' mode
for the shortest possible periods of time.
Special thanks to Matt Ragan for running my test kernels.
use the `a_entry' field from the kernel's header as a base.
Pass on a new DDB magic number to the kernel, so kernels linked for a
different KERNBASE value can apply a correction when booted from old
bootblocks.
prevents booting DDB kernels that are built with a different value of KERNBASE.
Apply a correction based on the magic number passed in by the bootblocks.
New bootblocks without the hard-coded KERNBASE reference will be assigned
a new magic number.
reset sequence to complete. Just sending the reset command and rushing
off -- like it used to do -- might cause the keyboard's response to get
lost in case the remaining kernel initialization decides to interact
with the console (RB_ASK!) by calling cngetc(), which goes off polling
within the PROM.
mycroft