summaryrefslogtreecommitdiff
path: root/rnd.h
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2018-12-10 14:13:34 +0100
committerTobias Klauser <tklauser@distanz.ch>2018-12-10 14:15:20 +0100
commit362019b833d715617488fdc3d5436d42babeb2b9 (patch)
tree32a15587144c53bf739c342b386f7f2d42d8cdc8 /rnd.h
parent1b966299df22a429d041e86300c928bb61d63ba5 (diff)
contrib: move auxiliary scripts to own directory
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'rnd.h')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-21 12:41:17 +0000
event-mon.c?h=nds-private-remove&id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7&id2=0c744ea4f77d72b3dcebb7a8f2684633ec79be88'>diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/gpio/gpio-event-mon.c')