From e993001f4772b543b1d3bd464e443b9e6a586199 Mon Sep 17 00:00:00 2001 From: pjd Date: Sun, 15 Oct 2006 12:40:27 +0000 Subject: Explain that using 64bit arguments on 32bit architectures with CTRx() macros is a bad idea. --- share/man/man9/ktr.9 | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'share/man') diff --git a/share/man/man9/ktr.9 b/share/man/man9/ktr.9 index 19b91de..b035991 100644 --- a/share/man/man9/ktr.9 +++ b/share/man/man9/ktr.9 @@ -145,3 +145,13 @@ It might be profitable at some point in time to use per-CPU buffers instead so that if one CPU halts or starts spinning, then the log messages it emitted just prior to halting or spinning will not be drowned out by events from the other CPUs. +.Pp +The arguments given in +.Fn CTRx +macros are stored as +.Vt u_long , +so don't pass arguments larger than size of an +.Vt u_long +type. +For example passing 64bit arguments on 32bit architectures will give incorrect +results. -- cgit v1.1