From 16a7f9e2bdd9ea2f4c05374fd65b16e072feea55 Mon Sep 17 00:00:00 2001 From: Glen Barber Date: Sat, 20 Oct 2012 23:13:09 +0000 Subject: [PATCH] Update ktr(4) to reflect changes from r239923. Reviewed by: attilio --- share/man/man4/ktr.4 | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/share/man/man4/ktr.4 b/share/man/man4/ktr.4 index 97981cececc..db61dfea6a4 100644 --- a/share/man/man4/ktr.4 +++ b/share/man/man4/ktr.4 @@ -24,7 +24,7 @@ .\" .\" $FreeBSD$ .\" -.Dd October 19, 2012 +.Dd October 20, 2012 .Dt KTR 4 .Os .Sh NAME @@ -85,6 +85,9 @@ Furthermore, there is a CPU event mask whose default value can be changed via the .Dv KTR_CPUMASK option. +When two or more parameters to +.Dv KTR_CPUMASK , +are used, it is important they are not separated by whitespace. A CPU must have the bit corresponding to its logical id set in this bitmask for events that occur on it to be logged. This mask can be set by the @@ -95,7 +98,12 @@ environment variable. It can also be examined and set after booting via the .Va debug.ktr.cpumask sysctl. -By default events on all CPUs are enabled. +By default, only CPUs specified in +.Dv KTR_CPUMASK +will log events. +See +.Pa sys/conf/NOTES +for more information. .Ss Verbose Mode By default, events are only logged to the internal buffer for examination later, but if the verbose flag is set then they are dumped to the kernel