summaryrefslogtreecommitdiff
path: root/tprintf.c
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2013-09-19 00:05:33 +0200
committerDaniel Borkmann <dborkman@redhat.com>2013-09-19 00:05:33 +0200
commitb009daf649bdc38080def483bbcf0165b9c2074e (patch)
tree30c637a3b87d764dc3416346bf03bac571950818 /tprintf.c
parent0450fd1d25b81e12908dfdac1819a571f10a8ee7 (diff)
doc: authors: moved Tobias one up
Nothing changes in that regard, Tobias and myself are both maintaining and continue to do so on one and the same level. Tobias does an awesome job, so this should be credited to him right here! Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'tprintf.c')
0 files changed, 0 insertions, 0 deletions
8194e4f6b6cae7&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/perf/tests/mmap-basic.c')