diff options
| author | Linus Torvalds <[email protected]> | 2024-07-29 12:05:06 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2024-07-29 12:05:06 -0700 |
| commit | cec6937dd1aae1b38d147bd190cb895d06cf96d0 (patch) | |
| tree | 971a172521f4d0d839a3737a8046b8a43c7d7601 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 2accfdb7eff65f390c4308b0e9cb7c3fe48ad63c (diff) | |
task_work: make TWA_NMI_CURRENT handling conditional on IRQ_WORK
The TWA_NMI_CURRENT handling very much depends on IRQ_WORK, but that
isn't universally enabled everywhere.
Maybe the IRQ_WORK infrastructure should just be unconditional - x86
ends up indirectly enabling it through unconditionally enabling
PERF_EVENTS, for example. But it also gets enabled by having SMP
support, or even if you just have PRINTK enabled.
But in the meantime TWA_NMI_CURRENT causes tons of build failures on
various odd minimal configs. Which did show up in linux-next, but
despite that nobody bothered to fix it or even inform me until -rc1 was
out.
Fixes: 466e4d801cd4 ("task_work: Add TWA_NMI_CURRENT as an additional notify mode")
Reported-by: Naresh Kamboju <[email protected]>
Reported-by: kernelci.org bot <[email protected]>
Reported-by: Guenter Roeck <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Sebastian Andrzej Siewior <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions