summaryrefslogtreecommitdiff
path: root/bpf_lexer.l
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2013-05-30 16:31:21 +0200
committerTobias Klauser <tklauser@distanz.ch>2013-05-30 16:34:01 +0200
commitc1aee513247783489c45507808b5a4589f6fb43a (patch)
tree407615b2cbe85e00fe9846ee2fef84881320123b /bpf_lexer.l
parent2e76c84b8e19ba02e82ce90370efe9feefd5a4b3 (diff)
netsniff-ng: Add __maybe_unused attribute to timer functions
The two functions timer_elapsed() and timer_next_dump() both take an argument which they don't use. Annotate them appropriately using the __maybe_unused attribute. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'bpf_lexer.l')
0 files changed, 0 insertions, 0 deletions
/div>
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/perf/tests/sdt.c')