summaryrefslogtreecommitdiff
path: root/curvetun
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2013-05-12 12:23:06 +0200
committerTobias Klauser <tklauser@distanz.ch>2013-05-12 12:31:03 +0200
commit6ce6b8b3d9ad6263848d6003b66c0a8f9bd80c4d (patch)
tree94864915b9e048d948d826aa8f1f3ddbfc1a94b7 /curvetun
parent255698e00c6200be70b6e72eec76c154249ac581 (diff)
dissector: ip_authentication_hdr: Remove trailing whitespaces
Remove two trailing whitespaces on emtpy lines. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'curvetun')
0 files changed, 0 insertions, 0 deletions
NR_CPUS.sh?id=0c744ea4f77d72b3dcebb7a8f2684633ec79be88'>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/testing/selftests/rcutorture/bin/configNR_CPUS.sh')