Date: Mon, 11 Dec 2000 17:01:50 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: RE: cvs commit: src/sys/kern kern_ktr.c Message-ID: <XFMail.001211170150.jhb@FreeBSD.org> In-Reply-To: <200012120043.eBC0hqx94479@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12-Dec-00 John Baldwin wrote: > jhb 2000/12/11 16:43:50 PST > > Modified files: > sys/kern kern_ktr.c > Log: > - Don't bother taking a trace message if we have panic'd since doing so > can lead to further panics. > - Call getnanotime() instead of nanotime() for the timestamp. nanotime() > is more precise, but it also calls into the timer code, which results > in mutex operations on the i386 arch. If KTR_LOCK is turned on, then > ktr_tracepoint() recurses on itself until it exhausts the kernel stack. > Eventually this should change to use get_cyclecount() instead, but that > can't happen if get_cyclecount() is calling nanotime() instead of > getnanotime(). If you have been suffering from double faults when enabling KTR_LOCK, this should fix that. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.001211170150.jhb>