From owner-freebsd-arch@FreeBSD.ORG Wed Feb 13 21:05:53 2013 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 96EFF99A; Wed, 13 Feb 2013 21:05:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 77742F45; Wed, 13 Feb 2013 21:05:52 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA12073; Wed, 13 Feb 2013 23:05:50 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1U5jWY-0000e8-FP; Wed, 13 Feb 2013 23:05:50 +0200 Message-ID: <511C002C.8090801@FreeBSD.org> Date: Wed, 13 Feb 2013 23:05:48 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130121 Thunderbird/17.0.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Proposal: Unify printing the function name in panic messages() References: <201302120134.r1C1Ycfh026347@chez.mckusick.com> <201302131504.19142.jhb@freebsd.org> <201302131511.14019.jhb@freebsd.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-arch@FreeBSD.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 21:05:53 -0000 on 13/02/2013 22:57 Adrian Chadd said the following: > Oh I'm not offended, feel free to be a bit of a jerk back to me. > > I'm just thinking of the longer term benefit here. If we _did_ tag > panic() messages with a globally unique panic string identifier we'd > make your job easier. > But yes, it's a longer term project.. Something of tangential relevance. In Linux they have some special trace code to debug ACPI resume issues that stores some IDs/hashes of trace statements (perhaps somewhat akin to our ktr) to RTC time-of-day registers. I guess that that was a smart choice because you can count on presence of those registers and they can be written with simple outb instructions. -- Andriy Gapon