Hi Keith,
How about changing things so that the kdbm_vm/kdbm_pg (and any future
modules) be compiled statically into the kernel?
Surely you would agree that the _only_ reason to have them as modules is
to be able to enhance kdb "on the fly" on a running system with some
exotic custom kernel features with the constraint of not being allowed to
reboot. This is probably a real-world situation in 0.0000% of the cases,
so I would suggest making them static not just by default but always.
But if you disagree, at least making this optional is, without a doubt, a
good idea.
Regards,
Tigran