- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Catch up with r243046. KTR buffer can be changed at runtime.

Update ktr(4) to reflect changes from r239923.

Reviewed by: attilio

- KTR_ENTRIES may be an arbitrary number, remove the sentence about
power of two.
- Mention the run time mask is set to block any tracing by default.

Reviewed by: jhb

Remove trailing whitespace per mdoc lint warning

Disussed with: gavin
No objection from: doc
Approved by: joel
MFC after: 3 days

Man page change to documant slight change in ktr_alq behaviour.

Strengthen wording; the KTR_ENTRIES value *must* be a power of two since
the code depends on this.

MFC after: 1 week

Bump the document date.

Forgotten by: ssouhlal, simon, trhodes
Approved by: grehan (mentor)

Mention that 'options ALQ' is required when using KTR_ALQ.

Approved by: simon, trhodes, grehan (mentor)

mdoc(7): Use the new feature of the .In macro.

mdoc(7) police: scheduled sweep.

Approved by: re

- Add a section on logging ktr entries to disk via ALQ.

- Move the description of KTR_CPUMASK into the "Event Masking" section.
- Remove the "Extensions" section since it is no longer relavent.
- Create a new section for KTR_VERBOSE and put it's description there.

- Remove the bogus reference to the removed KTR_EXTEND option.
- Add ktrdump(8) to the SEE ALSO section.
- Remove the BUGS section that complains about not having a userland utility
for viewing ktr data.

Use the .Bsx macro instead of .Tn BSD/OS.

Update history to reflect that ktr first appeared in BSD/OS 3.0.

mdoc(7) police: misc formatting fixes.

Document how to compile KTR into the kernel, tweak its behavior, and
examine the event logs in ddb(4).