Create a new header lwp_private.h to contain _lwp_getprivate_fast,
_lwp_gettcb_fast, _lwp_settcb and remove them from mcontext.h, so that:
1. we don't need special hacks to hide them
2. we can include <lwp.h> where needed to get the necessary prototypes
without redefining them locally.

branches: 1.1.2;
Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Clean up bootinfo startup:
- Be more explicit about whats PA vs VA, and make sure by the end of
bootinfo_startup1(), everything is set up for VA for subsequent
bootinfo calls.
- No longer need the "reloff" argument to bootinfo_startup2().

Split bootinfo_start() into bootinfo_startup1() (pre-MMU-enbled)
and bootinfo_startup2() (post-MMU-enabled). Use proper VA<->PA
relocation where called for (even though virt68k is VA==PA).

Move virt68k / bootinfo specific code out of pmap_bootstrap(),
and handle it in bootinfo_startup2().

Change bootinfo_start() to return the address representing the end
of the boot info structure. Use this in early bootstrap to avoid
a global reference before the MMU is enabled.

Add bootinfo_getarg(), which gets the name kernel command line argument
and returns its value (sort of like getenv()).

The RAM disk specified by bootinfo is not necessarily loaded along with
the static kernel image. Map is separately and account for it in the
available memory segments.

Detect a RND seed passed in by the loader.
XXX We don't actually *do* anything with it yet.

Move the initrd setup into bootinfo.c

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Largely unify the <machine/cpu.h> headers on the m68k platforms.

Adjust the clockframe to be the same as what the common m68k interrupt
dispatch code expects.

Make the M68K_MMU_* defines real kernel options, available in opt_m68k_arch.h.
For 68030, 68040, and 68060, infer M68K_MMU_MOTOROLA. For 68010 and 68020, it
must be an explicit option (set in std.${MACHINE} or, in the case of hp300,
inferred from the specific model option).

Remove duplicated / slightly-tweaked loadustp() (load user segment table)
routines from all of the m68k ports using the shared pmap. Instead, in
pmap_init(), set up a function pointer to the appropriate mmu_load_urp*()
function in mmu_subr.s.

Provide a mechanism for a system reset controller to register to be used
to reset/halt the system.

Collect some garbage.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Adjust the clockframe to be the same as what the common m68k interrupt
dispatch code expects.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

branches: 1.1.4;
Create a new header lwp_private.h to contain _lwp_getprivate_fast,
_lwp_gettcb_fast, _lwp_settcb and remove them from mcontext.h, so that:
1. we don't need special hacks to hide them
2. we can include <lwp.h> where needed to get the necessary prototypes
without redefining them locally.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Since we're batting 1.000 on "platforms that adopt new-pmap_68k that also
use machine_bootmap[]", just remove the option (it looks like it would
be opted into on every platform).

Introduce a hook for machine-specific code to influence pmap_bootstrap1()
in the new pmap_68k.

The pmap_bootmap structure allows machine-specific code to:
- Specify "keepout" ranges, intended to clamp the managed kernel address
space to keep it out of regions mapped using Transparent Translation
(usually devices).
- Allocate unmanaged kernel virtual address ranges (usually for devices).
- Optionally map physical addresses to those virtual address ranges (guess
what this might be used for!).

VM_MAX_KERNEL_ADDRESS is now run-time calculated. It starts off as
the very last page of the kernel virtual address space, and is reduced
as it encounters KEEPOUT areas.

Initially, use this on luna68k, news68k, and virt68k to KEEPOUT the
TT-mapped ranges.

While here, add some missing RELOC()s; no difference on VA==PA platforms,
but bound to blow up eventually.

Remove vestigal error checking.

__HAVE_NEW_PMAP_68K glue.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

__HAVE_NEW_PMAP_68K glue.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Hygiene.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Switch to common m68k vector table.

G/C unused P1PAGES.

Introduce a hook for machine-specific code to influence pmap_bootstrap1()
in the new pmap_68k.

The pmap_bootmap structure allows machine-specific code to:
- Specify "keepout" ranges, intended to clamp the managed kernel address
space to keep it out of regions mapped using Transparent Translation
(usually devices).
- Allocate unmanaged kernel virtual address ranges (usually for devices).
- Optionally map physical addresses to those virtual address ranges (guess
what this might be used for!).

VM_MAX_KERNEL_ADDRESS is now run-time calculated. It starts off as
the very last page of the kernel virtual address space, and is reduced
as it encounters KEEPOUT areas.

Initially, use this on luna68k, news68k, and virt68k to KEEPOUT the
TT-mapped ranges.

While here, add some missing RELOC()s; no difference on VA==PA platforms,
but bound to blow up eventually.

In the __HAVE_NEW_PMAP_68K case, don't need to leave room at the top
of the kernel VA space for kernel PTE array, because the new pmap doesn't
put it at a fixed address.

Remove vestigal error checking.

__HAVE_NEW_PMAP_68K glue.

Bump DFLSSIZ from 512KB to 2MB on all hp300 pmap m68k ports.

Some modern applications could require 512KB buffer on stack and
no particular comment on port-m68k@:
https://mail-index.netbsd.org/port-m68k/2025/02/02/msg000893.html

branches: 1.2.2;
The RAM disk specified by bootinfo is not necessarily loaded along with
the static kernel image. Map is separately and account for it in the
available memory segments.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.

Add a port to the Qemu m68k "virt" platform, a 68040-based virtual machine
with VirtIO I/O devices.

This is a work-in-progress, but "successfully mounts root file system
and then complains about missing /sbin/init that is, in fact, not there"
seems like a good checkpoint.