* [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends'
@ 2026-11-16 22:46 Brian Norris
2026-11-16 22:58 ` sashiko-bot
2026-11-17 13:53 ` Steven Rostedt
0 siblings, 2 replies; 13+ messages in thread
From: Brian Norris @ 2026-11-16 22:46 UTC (permalink / raw)
To: Steven Rostedt, Masami Hiramatsu
Cc: linux-kernel, linux-trace-kernel, Mathieu Desnoyers, Brian Norris
GENERIC_TRACER is not a user-selectable symbol, so it's impossible to
enable FTRACE_STARTUP_TEST unless one also enables some other symbol
that 'selects' GENERIC_TRACER for us.
This very file also suggests:
All tracer options should select GENERIC_TRACER
So, use 'select', not 'depends on'.
Fixes: 60a11774b38f ("ftrace: add self-tests")
Signed-off-by: Brian Norris <briannorris@chromium.org>
---
kernel/trace/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 35d043b19332..8084d46ef2a0 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -1135,7 +1135,7 @@ config FTRACE_SELFTEST
config FTRACE_STARTUP_TEST
bool "Perform a startup test on ftrace"
- depends on GENERIC_TRACER
+ select GENERIC_TRACER
select FTRACE_SELFTEST
help
This option performs a series of startup tests on ftrace. On bootup
--
2.56.1.703.gf848ed807c-goog
^ permalink raw reply related [flat|nested] 13+ messages in thread* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-16 22:46 [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' Brian Norris @ 2026-11-16 22:58 ` sashiko-bot 2026-11-17 13:55 ` Steven Rostedt 2026-11-17 13:53 ` Steven Rostedt 1 sibling, 1 reply; 13+ messages in thread From: sashiko-bot @ 2026-11-16 22:58 UTC (permalink / raw) To: Brian Norris; +Cc: linux-trace-kernel Thank you for your contribution! Sashiko AI review found 2 potential issues to consider: - [Low] tracing: FTRACE_STARTUP_TEST misuses select GENERIC_TRACER - [Low] tracing: inaccurate Fixes trailer commit in commit message -- commit 4d561c782a03c23e0e690cb6af78d98e81aa94d6 Author: Brian Norris <briannorris@chromium.org> > tracing: 'select' GENERIC_TRACER, not 'depends' > > GENERIC_TRACER is not a user-selectable symbol, so it's impossible to > enable FTRACE_STARTUP_TEST unless one also enables some other symbol > that 'selects' GENERIC_TRACER for us. > > This very file also suggests: > > All tracer options should select GENERIC_TRACER > > So, use 'select', not 'depends on'. > > Fixes: 60a11774b38f ("ftrace: add self-tests") > Signed-off-by: Brian Norris <briannorris@chromium.org> [Severity: Low] Commit 60a11774b38f ("ftrace: add self-tests") added FTRACE_STARTUP_TEST with "depends on TRACING" before GENERIC_TRACER existed. Should the Fixes tag instead reference 5e0a09391087 ("tracing: fix config options to not show when automatically selected"), which introduced GENERIC_TRACER and changed FTRACE_STARTUP_TEST to depend on it? > diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig > index c41397eccee50..347658dabbe33 100644 > --- a/kernel/trace/Kconfig > +++ b/kernel/trace/Kconfig > @@ -1135,7 +1135,7 @@ config FTRACE_SELFTEST > > config FTRACE_STARTUP_TEST > bool "Perform a startup test on ftrace" > - depends on GENERIC_TRACER > + select GENERIC_TRACER > select FTRACE_SELFTEST > help > This option performs a series of startup tests on ftrace. On bootup [Severity: Low] Should FTRACE_STARTUP_TEST depend on TRACING (or select TRACING) instead of selecting GENERIC_TRACER? GENERIC_TRACER is meant only for full tracer options so that ENABLE_DEFAULT_TRACERS is hidden when a full tracer is enabled: kernel/trace/Kconfig: # All tracer options should select GENERIC_TRACER. For those options that are # enabled by all tracers (context switch and event tracer) they select TRACING. ... config ENABLE_DEFAULT_TRACERS bool "Trace process context switches and events" depends on !GENERIC_TRACER select TRACING Because FTRACE_STARTUP_TEST is a test option rather than a tracer, having it select GENERIC_TRACER disables and hides ENABLE_DEFAULT_TRACERS when no full tracer is configured, and implicitly pulls in TRACING even when all tracers are disabled. -- Sashiko AI review · https://sashiko.dev/#/patchset/20261116144652.1.Iecb63200dd245f62032a3b1f60ae78cc48868094@changeid?part=1 ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-16 22:58 ` sashiko-bot @ 2026-11-17 13:55 ` Steven Rostedt 2026-11-17 18:23 ` Brian Norris 0 siblings, 1 reply; 13+ messages in thread From: Steven Rostedt @ 2026-11-17 13:55 UTC (permalink / raw) To: sashiko-bot; +Cc: sashiko-reviews, Brian Norris, linux-trace-kernel On Mon, 16 Nov 2026 22:58:01 +0000 sashiko-bot@kernel.org wrote: > [Severity: Low] > Should FTRACE_STARTUP_TEST depend on TRACING (or select TRACING) instead > of selecting GENERIC_TRACER? > > GENERIC_TRACER is meant only for full tracer options so that > ENABLE_DEFAULT_TRACERS is hidden when a full tracer is enabled: > > kernel/trace/Kconfig: > # All tracer options should select GENERIC_TRACER. For those options that are > # enabled by all tracers (context switch and event tracer) they select TRACING. > ... > config ENABLE_DEFAULT_TRACERS > bool "Trace process context switches and events" > depends on !GENERIC_TRACER > select TRACING > > Because FTRACE_STARTUP_TEST is a test option rather than a tracer, having > it select GENERIC_TRACER disables and hides ENABLE_DEFAULT_TRACERS when no > full tracer is configured, and implicitly pulls in TRACING even when all > tracers are disabled. Actually, the selftests should depend on TRACING and not GENERIC_TRACER. It may have been that the self tests were added before the trace events. But it should not "select" a config. The selftest are only to be selected if there is something to test. -- Steve ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 13:55 ` Steven Rostedt @ 2026-11-17 18:23 ` Brian Norris 2026-11-17 18:36 ` sashiko-bot 2026-11-17 19:22 ` Steven Rostedt 0 siblings, 2 replies; 13+ messages in thread From: Brian Norris @ 2026-11-17 18:23 UTC (permalink / raw) To: Steven Rostedt; +Cc: sashiko-bot, sashiko-reviews, linux-trace-kernel On Tue, Nov 17, 2026 at 08:55:52AM -0500, Steven Rostedt wrote: > On Mon, 16 Nov 2026 22:58:01 +0000 > sashiko-bot@kernel.org wrote: > > > [Severity: Low] > > Should FTRACE_STARTUP_TEST depend on TRACING (or select TRACING) instead > > of selecting GENERIC_TRACER? > > > > GENERIC_TRACER is meant only for full tracer options so that > > ENABLE_DEFAULT_TRACERS is hidden when a full tracer is enabled: > > > > kernel/trace/Kconfig: > > # All tracer options should select GENERIC_TRACER. For those options that are > > # enabled by all tracers (context switch and event tracer) they select TRACING. > > ... > > config ENABLE_DEFAULT_TRACERS > > bool "Trace process context switches and events" > > depends on !GENERIC_TRACER > > select TRACING > > > > Because FTRACE_STARTUP_TEST is a test option rather than a tracer, having > > it select GENERIC_TRACER disables and hides ENABLE_DEFAULT_TRACERS when no > > full tracer is configured, and implicitly pulls in TRACING even when all > > tracers are disabled. > > Actually, the selftests should depend on TRACING and not GENERIC_TRACER. It > may have been that the self tests were added before the trace events. > > But it should not "select" a config. The selftest are only to be selected > if there is something to test. OK, I can respin with 'depends on TRACING'. However, I think the Kconfig setup for kernel/trace/ is still a bit haphazard. For example, it's reasonably common to want EVENT_TRACING but not the more invasive tracing (like FUNCTION_TRACER; and therefore no GENERIC_TRACER) -- this is how all Android kernels are built, for one. But there's no user-configurable way to enable EVENT_TRACING. We only get it implicitly if something else inadvertently selects 'FTRACE' (which selects EVENT_TRACING). For Android, that's CONFIG_KPROBES and CONFIG_HIST_TRIGGERS. ...or is that what ENABLE_DEFAULT_TRACERS is? Its name doesn't really suggest that, and it's mutually exclusive witih many other tracers, so it's a bit awkward making choices, as the whole system appears much less orthogonal than expected. Anyway, my point is that it's not exactly straightforward to enable the features you want and get the tests you want. I've appended a diff that seems a bit more user-friendly to me. It makes it more explicit in the menu how event-tracing is forced-on by many other tracers, but is user-configurable when it's not forced. I can formally submit it (in 2 patches) if you'd like. Brian --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig @@ -198,6 +198,7 @@ config TRACING config GENERIC_TRACER bool select TRACING + select ENABLE_DEFAULT_TRACERS # # Minimum requirements an architecture has to meet for us to @@ -595,7 +596,6 @@ config MMIOTRACE config ENABLE_DEFAULT_TRACERS bool "Trace process context switches and events" - depends on !GENERIC_TRACER select TRACING help This tracer hooks to various trace points in the kernel, @@ -1135,7 +1135,7 @@ config FTRACE_SELFTEST config FTRACE_STARTUP_TEST bool "Perform a startup test on ftrace" - depends on GENERIC_TRACER + depends on TRACING select FTRACE_SELFTEST help This option performs a series of startup tests on ftrace. On bootup ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 18:23 ` Brian Norris @ 2026-11-17 18:36 ` sashiko-bot 2026-11-17 18:42 ` Brian Norris 2026-11-17 19:22 ` Steven Rostedt 1 sibling, 1 reply; 13+ messages in thread From: sashiko-bot @ 2026-11-17 18:36 UTC (permalink / raw) To: Brian Norris; +Cc: linux-trace-kernel Thank you for your contribution! Sashiko AI review found 2 potential issues to consider: - [High] tracing: missing Signed-off-by trailer and unformatted email reply changelog - [Low] tracing: ENABLE_DEFAULT_TRACERS stays unselected for direct TRACING selectors -- commit 3e6de7d49bb4a2d1503d2aeab72b682a01dfe176 Author: Brian Norris <briannorris@chromium.org> > tracing: 'select' GENERIC_TRACER, not 'depends' > > On Tue, Nov 17, 2026 at 08:55:52AM -0500, Steven Rostedt wrote: > > On Mon, 16 Nov 2026 22:58:01 +0000 > > sashiko-bot@kernel.org wrote: > > > > > [Severity: Low] > > > Should FTRACE_STARTUP_TEST depend on TRACING (or select TRACING) instead > > > of selecting GENERIC_TRACER? > > > > > > GENERIC_TRACER is meant only for full tracer options so that > > > ENABLE_DEFAULT_TRACERS is hidden when a full tracer is enabled: > > > > > > kernel/trace/Kconfig: > > > # All tracer options should select GENERIC_TRACER. For those options that are > > > # enabled by all tracers (context switch and event tracer) they select TRACING. > > > ... > > > config ENABLE_DEFAULT_TRACERS > > > bool "Trace process context switches and events" > > > depends on !GENERIC_TRACER > > > select TRACING > > > > > > Because FTRACE_STARTUP_TEST is a test option rather than a tracer, having > > > it select GENERIC_TRACER disables and hides ENABLE_DEFAULT_TRACERS when no > > > full tracer is configured, and implicitly pulls in TRACING even when all > > > tracers are disabled. > > > > Actually, the selftests should depend on TRACING and not GENERIC_TRACER. It > > may have been that the self tests were added before the trace events. > > > > But it should not "select" a config. The selftest are only to be selected > > if there is something to test. > > OK, I can respin with 'depends on TRACING'. > > However, I think the Kconfig setup for kernel/trace/ is still a bit > haphazard. For example, it's reasonably common to want EVENT_TRACING but > not the more invasive tracing (like FUNCTION_TRACER; and therefore no > GENERIC_TRACER) -- this is how all Android kernels are built, for one. > > But there's no user-configurable way to enable EVENT_TRACING. We only > get it implicitly if something else inadvertently selects 'FTRACE' > (which selects EVENT_TRACING). For Android, that's CONFIG_KPROBES and > CONFIG_HIST_TRIGGERS. > > ...or is that what ENABLE_DEFAULT_TRACERS is? Its name doesn't really > suggest that, and it's mutually exclusive witih many other tracers, so > it's a bit awkward making choices, as the whole system appears much less > orthogonal than expected. > > Anyway, my point is that it's not exactly straightforward to enable the > features you want and get the tests you want. > > I've appended a diff that seems a bit more user-friendly to me. It > makes it more explicit in the menu how event-tracing is forced-on by > many other tracers, but is user-configurable when it's not forced. I can > formally submit it (in 2 patches) if you'd like. > > Brian [Severity: High] This commit is missing a Signed-off-by trailer, its body is an unedited mailing-list reply rather than a commit changelog, and the subject line states the opposite of the FTRACE_STARTUP_TEST change (which switches "depends on GENERIC_TRACER" to "depends on TRACING"). > diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig > index c41397eccee50..f49397f7c92d6 100644 > --- a/kernel/trace/Kconfig > +++ b/kernel/trace/Kconfig > @@ -198,6 +198,7 @@ config TRACING > config GENERIC_TRACER > bool > select TRACING > + select ENABLE_DEFAULT_TRACERS > > # > # Minimum requirements an architecture has to meet for us to > @@ -595,7 +596,6 @@ config MMIOTRACE > > config ENABLE_DEFAULT_TRACERS > bool "Trace process context switches and events" > - depends on !GENERIC_TRACER > select TRACING > help > This tracer hooks to various trace points in the kernel, [Severity: Low] Does ENABLE_DEFAULT_TRACERS remain unselected when TRACING is enabled by options that do not select GENERIC_TRACER? Options such as KPROBE_EVENTS and HIST_TRIGGERS select TRACING directly (which in turn selects EVENT_TRACING and CONTEXT_SWITCH_TRACER) without selecting GENERIC_TRACER. When those options are enabled with GENERIC_TRACER=n, event tracing is already forced on, but ENABLE_DEFAULT_TRACERS stays n and appears in menuconfig as a mutable toggle that has no effect on the build. Also, the comment above config TRACING still explains that GENERIC_TRACER and TRACING are separate so that ENABLE_DEFAULT_TRACERS is hidden when selected by another tracer, which no longer matches the Kconfig logic once "depends on !GENERIC_TRACER" is removed. -- Sashiko AI review · https://sashiko.dev/#/patchset/avybp3O2zxcLozKB@google.com?part=1 ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 18:36 ` sashiko-bot @ 2026-11-17 18:42 ` Brian Norris 0 siblings, 0 replies; 13+ messages in thread From: Brian Norris @ 2026-11-17 18:42 UTC (permalink / raw) To: sashiko-reviews; +Cc: linux-trace-kernel On Tue, Nov 17, 2026 at 06:36:09PM +0000, sashiko-bot@kernel.org wrote: > Thank you for your contribution! Sashiko AI review found 2 potential > issues to consider: > - [High] tracing: missing Signed-off-by trailer and unformatted email > reply changelog > - [Low] tracing: ENABLE_DEFAULT_TRACERS stays unselected for direct > TRACING selectors > -- > > Anyway, my point is that it's not exactly straightforward to enable the > > features you want and get the tests you want. > > > > I've appended a diff that seems a bit more user-friendly to me. It > > makes it more explicit in the menu how event-tracing is forced-on by > > many other tracers, but is user-configurable when it's not forced. I can > > formally submit it (in 2 patches) if you'd like. Well clearly sashiko still points out issues here. But I still maintain that the config menu here is confusing and hard to use. I'll see if I can come up with a better solution, or else just accept the un-friendliness. Brian ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 18:23 ` Brian Norris 2026-11-17 18:36 ` sashiko-bot @ 2026-11-17 19:22 ` Steven Rostedt 2026-11-17 19:23 ` Steven Rostedt 1 sibling, 1 reply; 13+ messages in thread From: Steven Rostedt @ 2026-11-17 19:22 UTC (permalink / raw) To: Brian Norris; +Cc: sashiko-bot, sashiko-reviews, linux-trace-kernel On Tue, 17 Nov 2026 10:23:35 -0800 Brian Norris <briannorris@chromium.org> wrote: > > OK, I can respin with 'depends on TRACING'. > > However, I think the Kconfig setup for kernel/trace/ is still a bit > haphazard. For example, it's reasonably common to want EVENT_TRACING but > not the more invasive tracing (like FUNCTION_TRACER; and therefore no > GENERIC_TRACER) -- this is how all Android kernels are built, for one. > > But there's no user-configurable way to enable EVENT_TRACING. We only > get it implicitly if something else inadvertently selects 'FTRACE' > (which selects EVENT_TRACING). For Android, that's CONFIG_KPROBES and > CONFIG_HIST_TRIGGERS. > > ...or is that what ENABLE_DEFAULT_TRACERS is? Its name doesn't really > suggest that, and it's mutually exclusive witih many other tracers, so > it's a bit awkward making choices, as the whole system appears much less > orthogonal than expected. Yes, it's the ENABLE_DEFAULT_TRACERS that is what I think you want. It's a horrible name and should be changed as it's terminology is a left over from the early days of ftrace where tracers were everything and the "nop" (default) was the tracer that let you select events. The haphazard way that Kconfig is set up is due to the evolution of the tracing subsystem where things evolved through mutations. That Kconfig is just a nice paleontology case of ftrace. I think it would be good to rename that specific config, and also move it to the top of the Tracing menu that says: Enable trace events As all tracers enable events, it doesn't need to be visible when GENERIC_TRACER is enabled. This is the way to enable events when no tracer is defined. > > Anyway, my point is that it's not exactly straightforward to enable the > features you want and get the tests you want. Yes, lets fix that. > > I've appended a diff that seems a bit more user-friendly to me. It > makes it more explicit in the menu how event-tracing is forced-on by > many other tracers, but is user-configurable when it's not forced. I can > formally submit it (in 2 patches) if you'd like. Let's do one patch that changes the name and prompt of the ENABLE_DEFAULT_TRACERS. Basically: config ENABLE_EVENTS bool "Enable trace events" help Select this to enable trace events through out the kernel such as scheduling, irq, kmalloc that can record to the tracefs ring buffer data from within the subsystems the events exist in. or something like that. -- Steve ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 19:22 ` Steven Rostedt @ 2026-11-17 19:23 ` Steven Rostedt 2026-11-17 20:35 ` Brian Norris 0 siblings, 1 reply; 13+ messages in thread From: Steven Rostedt @ 2026-11-17 19:23 UTC (permalink / raw) To: Brian Norris; +Cc: sashiko-bot, sashiko-reviews, linux-trace-kernel On Tue, 17 Nov 2026 14:22:03 -0500 Steven Rostedt <rostedt@goodmis.org> wrote: As it doesn't need to be visible let's still have: > config ENABLE_EVENTS > bool "Enable trace events" depends on !GENERIC_TRACER select TRACING > help > Select this to enable trace events through out the kernel such as > scheduling, irq, kmalloc that can record to the tracefs ring > buffer data from within the subsystems the events exist in. -- Steve ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 19:23 ` Steven Rostedt @ 2026-11-17 20:35 ` Brian Norris 2026-11-17 21:10 ` Steven Rostedt 0 siblings, 1 reply; 13+ messages in thread From: Brian Norris @ 2026-11-17 20:35 UTC (permalink / raw) To: Steven Rostedt; +Cc: sashiko-bot, sashiko-reviews, linux-trace-kernel On Tue, Nov 17, 2026 at 02:23:10PM -0500, Steven Rostedt wrote: > On Tue, 17 Nov 2026 14:22:03 -0500 > Steven Rostedt <rostedt@goodmis.org> wrote: > > As it doesn't need to be visible let's still have: What's wrong with visible? Hiding it is part of the confusion, because it disappears when you select something else, even though it's still effectively enabled. Personally, I think it would be nicer if we could eliminate the separate ENABLE_DEFAULT_TRACERS (or ENABLE_EVENTS or whatever you want to call it) and make CONFIG_EVENT_TRACING: 1) user-configurable and 2) 'select'ed (or otherwise forced to =y) when something else truly requires it That would make it clearer what's happening, IMO. But I'm not sure off the top of my head what the best way to do that in Kconfig is, without introducing odd circular dependencies or other issues, and I also don't know how much more time I want to spend on it. I'm open to ideas, or I'll let it sit/marinate until I have more time. Brian > > > config ENABLE_EVENTS > > bool "Enable trace events" > depends on !GENERIC_TRACER > select TRACING > > help > > Select this to enable trace events through out the kernel such as > > scheduling, irq, kmalloc that can record to the tracefs ring > > buffer data from within the subsystems the events exist in. > > > -- Steve ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 20:35 ` Brian Norris @ 2026-11-17 21:10 ` Steven Rostedt 2026-11-17 21:41 ` Brian Norris 0 siblings, 1 reply; 13+ messages in thread From: Steven Rostedt @ 2026-11-17 21:10 UTC (permalink / raw) To: Brian Norris; +Cc: sashiko-bot, sashiko-reviews, linux-trace-kernel On Tue, 17 Nov 2026 12:35:41 -0800 Brian Norris <briannorris@chromium.org> wrote: > On Tue, Nov 17, 2026 at 02:23:10PM -0500, Steven Rostedt wrote: > > On Tue, 17 Nov 2026 14:22:03 -0500 > > Steven Rostedt <rostedt@goodmis.org> wrote: > > > > As it doesn't need to be visible let's still have: > > What's wrong with visible? Hiding it is part of the confusion, because > it disappears when you select something else, even though it's still > effectively enabled. Well, one thing, it's precedence. But another is that you can only deselect it if everything else is not selected. > > Personally, I think it would be nicer if we could eliminate the separate > ENABLE_DEFAULT_TRACERS (or ENABLE_EVENTS or whatever you want to call > it) and make CONFIG_EVENT_TRACING: I think that may have been the reason for the craziness to begin with. I do remember struggling with circular dependencies. > > 1) user-configurable and > 2) 'select'ed (or otherwise forced to =y) when something else truly > requires it > > That would make it clearer what's happening, IMO. > > But I'm not sure off the top of my head what the best way to do that in > Kconfig is, without introducing odd circular dependencies or other > issues, and I also don't know how much more time I want to spend on it. > > I'm open to ideas, or I'll let it sit/marinate until I have more time. I'm in no rush ;-) -- Steve ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 21:10 ` Steven Rostedt @ 2026-11-17 21:41 ` Brian Norris 0 siblings, 0 replies; 13+ messages in thread From: Brian Norris @ 2026-11-17 21:41 UTC (permalink / raw) To: Steven Rostedt; +Cc: sashiko-bot, sashiko-reviews, linux-trace-kernel On Tue, Nov 17, 2026 at 04:10:11PM -0500, Steven Rostedt wrote: > On Tue, 17 Nov 2026 12:35:41 -0800 > Brian Norris <briannorris@chromium.org> wrote: > > > On Tue, Nov 17, 2026 at 02:23:10PM -0500, Steven Rostedt wrote: > > > On Tue, 17 Nov 2026 14:22:03 -0500 > > > Steven Rostedt <rostedt@goodmis.org> wrote: > > > > > > As it doesn't need to be visible let's still have: > > > > What's wrong with visible? Hiding it is part of the confusion, because > > it disappears when you select something else, even though it's still > > effectively enabled. > > Well, one thing, it's precedence. Do you mean: because that's how you've done it previously? Or precedence, as in "other tracers take precedence over a visible EVENT_TRACING"? > But another is that you can only deselect > it if everything else is not selected. Right, but that's pretty typical of interdependent features, I think. And it's explicitly represented in the menu: - the non-deselectable item loses its box, to represent that it's no longer a checkbox that can be unchecked - if one wants to drill into "why can't I uncheck?", the Help option gives a good breakdown, with something like: Selected by [y]: - GENERIC_TRACER [=y] That gives you a burn-down of what other things must be disabled if you want to disable it. Brian ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-16 22:46 [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' Brian Norris 2026-11-16 22:58 ` sashiko-bot @ 2026-11-17 13:53 ` Steven Rostedt 2026-11-17 17:45 ` Brian Norris 1 sibling, 1 reply; 13+ messages in thread From: Steven Rostedt @ 2026-11-17 13:53 UTC (permalink / raw) To: Brian Norris Cc: Masami Hiramatsu, linux-kernel, linux-trace-kernel, Mathieu Desnoyers On Mon, 16 Nov 2026 14:46:53 -0800 Brian Norris <briannorris@chromium.org> wrote: > GENERIC_TRACER is not a user-selectable symbol, so it's impossible to > enable FTRACE_STARTUP_TEST unless one also enables some other symbol > that 'selects' GENERIC_TRACER for us. I believe that was the way it was intended. The selftests are to test the things that select GENERIC_TRACER. Why would we enable tests for something that isn't enabled? -- Steve > > This very file also suggests: > > All tracer options should select GENERIC_TRACER > > So, use 'select', not 'depends on'. > > Fixes: 60a11774b38f ("ftrace: add self-tests") > Signed-off-by: Brian Norris <briannorris@chromium.org> > --- ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' 2026-11-17 13:53 ` Steven Rostedt @ 2026-11-17 17:45 ` Brian Norris 0 siblings, 0 replies; 13+ messages in thread From: Brian Norris @ 2026-11-17 17:45 UTC (permalink / raw) To: Steven Rostedt Cc: Masami Hiramatsu, linux-kernel, linux-trace-kernel, Mathieu Desnoyers On Tue, Nov 17, 2026 at 08:53:17AM -0500, Steven Rostedt wrote: > On Mon, 16 Nov 2026 14:46:53 -0800 > Brian Norris <briannorris@chromium.org> wrote: > > > GENERIC_TRACER is not a user-selectable symbol, so it's impossible to > > enable FTRACE_STARTUP_TEST unless one also enables some other symbol > > that 'selects' GENERIC_TRACER for us. > > I believe that was the way it was intended. The selftests are to test the > things that select GENERIC_TRACER. Why would we enable tests for something > that isn't enabled? You may have discovered in your other reply, but these tests are applicable to code used by EVENT_TRACING, which can be enabled without GENERIC_TRACER. But I do see how this still might not be exactly the right choice, especially given some of sashiko's comments. Brian ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2026-11-17 21:41 UTC | newest] Thread overview: 13+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2026-11-16 22:46 [PATCH] tracing: 'select' GENERIC_TRACER, not 'depends' Brian Norris 2026-11-16 22:58 ` sashiko-bot 2026-11-17 13:55 ` Steven Rostedt 2026-11-17 18:23 ` Brian Norris 2026-11-17 18:36 ` sashiko-bot 2026-11-17 18:42 ` Brian Norris 2026-11-17 19:22 ` Steven Rostedt 2026-11-17 19:23 ` Steven Rostedt 2026-11-17 20:35 ` Brian Norris 2026-11-17 21:10 ` Steven Rostedt 2026-11-17 21:41 ` Brian Norris 2026-11-17 13:53 ` Steven Rostedt 2026-11-17 17:45 ` Brian Norris
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox