From owner-cvs-all  Mon Dec 11 16:43:55 2000
From owner-cvs-all@FreeBSD.ORG  Mon Dec 11 16:43:52 2000
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8266737B400; Mon, 11 Dec 2000 16:43:52 -0800 (PST)
Received: (from jhb@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id eBC0hqx94479;
	Mon, 11 Dec 2000 16:43:52 -0800 (PST)
	(envelope-from jhb)
Message-Id: <200012120043.eBC0hqx94479@freefall.freebsd.org>
From: John Baldwin <jhb@FreeBSD.org>
Date: Mon, 11 Dec 2000 16:43:50 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/kern kern_ktr.c
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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().
  
  Revision  Changes    Path
  1.7       +4 -2      src/sys/kern/kern_ktr.c



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message