Date: Wed, 13 Feb 2013 23:05:48 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Adrian Chadd <adrian@FreeBSD.org> Cc: freebsd-arch@FreeBSD.org Subject: Re: Proposal: Unify printing the function name in panic messages() Message-ID: <511C002C.8090801@FreeBSD.org> In-Reply-To: <CAJ-Vmong=OW-243rVYh%2BWc4dwQDWbynHkKcEr3Zp3RD2-2_L4g@mail.gmail.com> References: <201302120134.r1C1Ycfh026347@chez.mckusick.com> <CAJ-Vmo=wwFD7_OF%2BFdJkPyxjQD_4y-yBU6guUHTuCkFr%2BoYh-w@mail.gmail.com> <201302131504.19142.jhb@freebsd.org> <201302131511.14019.jhb@freebsd.org> <CAJ-Vmong=OW-243rVYh%2BWc4dwQDWbynHkKcEr3Zp3RD2-2_L4g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?511C002C.8090801>