Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Nov 2021 17:39:04 +0000
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        "Mitchell Horne" <mhorne@freebsd.org>
Cc:        freebsd-arch@freebsd.org, freebsd-hackers@freebsd.org, cperciva@freebsd.org
Subject:   Re: A new boot-time trace framework
Message-ID:  <5E5F06E4-F0FA-45F9-B121-88C69CA15A25@lists.zabbadoz.net>
In-Reply-To: <deee2c46-c3ed-3c0f-1d7a-3321b4fe9a7c@freebsd.org>
References:  <deee2c46-c3ed-3c0f-1d7a-3321b4fe9a7c@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Nov 2021, at 16:26, Mitchell Horne wrote:

> Unlike TSLOG, I intend for this work to be compiled in to the kernel 
> by default, but disabled behind a tunable (kern.boottrace.enabled). 
> The cost of doing so should be minimal, only a couple of syscalls 
> added to init(8) at most.

I think if you really want to have this on by default (whether that make 
sense or not for the majority of people) I’d at least avoid the 
function call and reduce it to a branch which is super-easy to do.

My honest feeling is that another of the at least 3 other tracing 
mechanisms existing these days be better extended and improved rather 
than another one added;  we were always joking about 3 firewalls but if 
we keep going this path we can soon start joking about 9 tracing 
mechanisms and that will be a major mess for sysadmins.  I can see from 
when this work was coming and back then it might have made sense this 
way; but more than a decade has passed..

/bz



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5E5F06E4-F0FA-45F9-B121-88C69CA15A25>