From owner-cvs-all Tue Jun 26 20:32:11 2001 Delivered-To: cvs-all@freebsd.org Received: from server.baldwin.cx (server.baldwin.cx [204.216.28.80]) by hub.freebsd.org (Postfix) with ESMTP id AAD5737B401; Tue, 26 Jun 2001 20:32:06 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (tserver.conference.usenix.org [199.103.159.3]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id UAA20191; Tue, 26 Jun 2001 20:33:35 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200106252309.f5PN9Wn65534@freefall.freebsd.org> Date: Tue, 26 Jun 2001 20:32:05 -0700 (PDT) From: John Baldwin To: John Baldwin Subject: RE: cvs commit: src/sys/kern kern_ktr.c src/sys/sys ktr.h Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 25-Jun-01 John Baldwin wrote: > jhb 2001/06/25 16:09:32 PDT > > Modified files: > sys/kern kern_ktr.c > sys/sys ktr.h > Log: > ... > - Fiddle with the ktr_cpumask in ktr_tracepoint() to disable KTR events > on the current CPU while we are processing an event. In theory this means that using nanotime instead of getnanotime in the KTR_LOCK and/or KTR_WITNESS cases shouldn't recurse anymore, and in fact, it works fine on the alpha, but on x86 I still get weird double fault panics (I assume from exhausting the stack) and haven't been able to get a useful traceback or anything else to figure out where and why it is breaking, so I've left the hack to use getnanotime in for now. -- John Baldwin -- 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