[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251219132812.2a3516df@gandalf.local.home>
Date: Fri, 19 Dec 2025 13:28:12 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Theodore Tso <tytso@....edu>, Julia Lawall <julia.lawall@...ia.fr>,
"Paul E. McKenney" <paulmck@...nel.org>, Gabriele Paoloni
<gpaoloni@...hat.com>, Kate Stewart <kstewart@...uxfoundation.org>, Chuck
Wolber <chuckwolber@...il.com>, Dmitry Vyukov <dvyukov@...gle.com>, Mark
Rutland <mark.rutland@....com>, Thomas Gleixner <tglx@...utronix.de>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, Shuah Khan
<skhan@...uxfoundation.org>, Chris Mason <clm@...a.com>,
linux-kernel@...r.kernel.org
Subject: Re: Follow-up on Linux-kernel code accessibility
On Fri, 19 Dec 2025 12:59:42 -0500
Sasha Levin <sashal@...nel.org> wrote:
> I'd we weary to see complex specs in kernel-internal functions. Those often get
> refactored and improved. Having complex speccing on them will make that work
> much more difficult and complex.
I would argue that having a module describing a complex portion of the
kernel functions would be useful for not only helping to understand those
functions, but also possibly making it easier to see how they can be
improved upon.
This is one of the motivations I have for modeling the complex portions of
the tracing subsystem. I'm hoping that I can see better ways to perform
these tasks and possibly even improve its performance.
-- Steve
Powered by blists - more mailing lists