Finish converting ddb_sysctl to sysctl_int_bounded

I missed the verbose pattern that it used for error checking the first
time around.

OK millert@

Convert ddb_sysctl to sysctl_bounded_arr

ok gkoehler@

If you use sys/param.h, you don't need sys/types.h

Rename Debugger() into db_enter().

Using a name with the 'db_' prefix makes it invisible from the dynamic
profiler.

ok deraadt@, kettenis@, visa@

Introduce Dynamic Profiling, a ddb(4) based & gprof compatible kernel
profiling framework.

Code patching is used to enable probes when entering functions. The
probes will call a mcount()-like function to match the behavior of a
GPROF kernel.

Currently only available on amd64 and guarded under DDBPROF. Support
for other archs will follow soon.

A new sysctl knob, ddb.console, need to be set to 1 in securelevel 0
to be able to use this feature.

Inputs and ok guenther@

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

These do not need the extremely poorly named uvm/uvm_extern.h (which
pulls in the universe). occasionally they need sys/systm.h

If sysctl ddb.trigger=1 is not called from the console, the error
message "value is not available" was misleading. Use the ENODEV
error to generate the more appropriate message "Operation not
supported by device". Note that ddb.console must be set to 1 to
see that error at all.
OK mpf@

Correct the links between threads, processes, pgrps, and sessions,
so that the process-level stuff is to/from struct process and not
struct proc. This fixes a bunch of problem cases in rthreads.
Based on earlier work by blambert and myself, but mostly written
at c2k10.

Tested by many: deraadt, sthen, krw, ray, and in snapshots

Add a new sysctl ``ddb.trigger''
Writing to it, will bring the system into the kernel debugger.
ddb.console=1 is required and the sysctl command has to be executed
from the actual console tty.
If the securelevel is < 1, the tty check is ignored.
Feedback and OK ckuethe@, deraadt@.

Still allow ddb.console and ddb.panic to be raised if securelevel <= 0;
ok deraadt@

use sysctl_int_lower (old code had the negative bug)

ansi/deregister. No binary change.

default db.log=1. as noted by Sam Smith, this is more useful. mickey concurred

option to log ddb output to kernel message buffer, via sysctl ddb.log
ok deraadt@ henric@ djm@

kill the clauses three and four on my sources

Don't let variable declarations without "extern" living in .h files.
While there fix a benign type mismatch in db_stack_dump() and remove
diag code left by art by mistake.

branches: 1.5.2;
Replace inclusion of <vm/foo.h> with the correct <uvm/bar.h> when necessary.
(Look ma, I might have broken the tree)

Provide a means to lock ddb off on systems at high securelevel, in order
reduce the need for a custom kernel sans ddb.

branches: 1.3.10;
rename ddb.panic_ddb, and add ddb.console. Now you can stop console ddb entry
with a sysctl. There will be architectures and drivers that lack function,
and I trust the maintainers of those will forget to add the code..

sysctl ddb.panic_ddb; felix@mamba.pond.sub.org

Added: sysctl access to the ddb variables.
Fixed: "netbsd" strings in sym table handling routines.
now it is usefull to change max_{width,line} according
to your real console geometry, just w/ sysctl program.

Convert ddb_sysctl to sysctl_bounded_arr

ok gkoehler@

If you use sys/param.h, you don't need sys/types.h

Rename Debugger() into db_enter().

Using a name with the 'db_' prefix makes it invisible from the dynamic
profiler.

ok deraadt@, kettenis@, visa@

Introduce Dynamic Profiling, a ddb(4) based & gprof compatible kernel
profiling framework.

Code patching is used to enable probes when entering functions. The
probes will call a mcount()-like function to match the behavior of a
GPROF kernel.

Currently only available on amd64 and guarded under DDBPROF. Support
for other archs will follow soon.

A new sysctl knob, ddb.console, need to be set to 1 in securelevel 0
to be able to use this feature.

Inputs and ok guenther@

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

These do not need the extremely poorly named uvm/uvm_extern.h (which
pulls in the universe). occasionally they need sys/systm.h

If sysctl ddb.trigger=1 is not called from the console, the error
message "value is not available" was misleading. Use the ENODEV
error to generate the more appropriate message "Operation not
supported by device". Note that ddb.console must be set to 1 to
see that error at all.
OK mpf@

Correct the links between threads, processes, pgrps, and sessions,
so that the process-level stuff is to/from struct process and not
struct proc. This fixes a bunch of problem cases in rthreads.
Based on earlier work by blambert and myself, but mostly written
at c2k10.

Tested by many: deraadt, sthen, krw, ray, and in snapshots

Add a new sysctl ``ddb.trigger''
Writing to it, will bring the system into the kernel debugger.
ddb.console=1 is required and the sysctl command has to be executed
from the actual console tty.
If the securelevel is < 1, the tty check is ignored.
Feedback and OK ckuethe@, deraadt@.

Still allow ddb.console and ddb.panic to be raised if securelevel <= 0;
ok deraadt@

use sysctl_int_lower (old code had the negative bug)

ansi/deregister. No binary change.

default db.log=1. as noted by Sam Smith, this is more useful. mickey concurred

option to log ddb output to kernel message buffer, via sysctl ddb.log
ok deraadt@ henric@ djm@

kill the clauses three and four on my sources

Don't let variable declarations without "extern" living in .h files.
While there fix a benign type mismatch in db_stack_dump() and remove
diag code left by art by mistake.

branches: 1.5.2;
Replace inclusion of <vm/foo.h> with the correct <uvm/bar.h> when necessary.
(Look ma, I might have broken the tree)

Provide a means to lock ddb off on systems at high securelevel, in order
reduce the need for a custom kernel sans ddb.

branches: 1.3.10;
rename ddb.panic_ddb, and add ddb.console. Now you can stop console ddb entry
with a sysctl. There will be architectures and drivers that lack function,
and I trust the maintainers of those will forget to add the code..

sysctl ddb.panic_ddb; felix@mamba.pond.sub.org

Added: sysctl access to the ddb variables.
Fixed: "netbsd" strings in sym table handling routines.
now it is usefull to change max_{width,line} according
to your real console geometry, just w/ sysctl program.

If you use sys/param.h, you don't need sys/types.h

Rename Debugger() into db_enter().

Using a name with the 'db_' prefix makes it invisible from the dynamic
profiler.

ok deraadt@, kettenis@, visa@

Introduce Dynamic Profiling, a ddb(4) based & gprof compatible kernel
profiling framework.

Code patching is used to enable probes when entering functions. The
probes will call a mcount()-like function to match the behavior of a
GPROF kernel.

Currently only available on amd64 and guarded under DDBPROF. Support
for other archs will follow soon.

A new sysctl knob, ddb.console, need to be set to 1 in securelevel 0
to be able to use this feature.

Inputs and ok guenther@

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

These do not need the extremely poorly named uvm/uvm_extern.h (which
pulls in the universe). occasionally they need sys/systm.h

If sysctl ddb.trigger=1 is not called from the console, the error
message "value is not available" was misleading. Use the ENODEV
error to generate the more appropriate message "Operation not
supported by device". Note that ddb.console must be set to 1 to
see that error at all.
OK mpf@

Correct the links between threads, processes, pgrps, and sessions,
so that the process-level stuff is to/from struct process and not
struct proc. This fixes a bunch of problem cases in rthreads.
Based on earlier work by blambert and myself, but mostly written
at c2k10.

Tested by many: deraadt, sthen, krw, ray, and in snapshots

Add a new sysctl ``ddb.trigger''
Writing to it, will bring the system into the kernel debugger.
ddb.console=1 is required and the sysctl command has to be executed
from the actual console tty.
If the securelevel is < 1, the tty check is ignored.
Feedback and OK ckuethe@, deraadt@.

Still allow ddb.console and ddb.panic to be raised if securelevel <= 0;
ok deraadt@

use sysctl_int_lower (old code had the negative bug)

ansi/deregister. No binary change.

default db.log=1. as noted by Sam Smith, this is more useful. mickey concurred

option to log ddb output to kernel message buffer, via sysctl ddb.log
ok deraadt@ henric@ djm@

kill the clauses three and four on my sources

Don't let variable declarations without "extern" living in .h files.
While there fix a benign type mismatch in db_stack_dump() and remove
diag code left by art by mistake.

branches: 1.5.2;
Replace inclusion of <vm/foo.h> with the correct <uvm/bar.h> when necessary.
(Look ma, I might have broken the tree)

Provide a means to lock ddb off on systems at high securelevel, in order
reduce the need for a custom kernel sans ddb.

branches: 1.3.10;
rename ddb.panic_ddb, and add ddb.console. Now you can stop console ddb entry
with a sysctl. There will be architectures and drivers that lack function,
and I trust the maintainers of those will forget to add the code..

sysctl ddb.panic_ddb; felix@mamba.pond.sub.org

Added: sysctl access to the ddb variables.
Fixed: "netbsd" strings in sym table handling routines.
now it is usefull to change max_{width,line} according
to your real console geometry, just w/ sysctl program.