#!/bin/sh # description: event trigger - test multiple histogram triggers do_reset() { reset_trigger echo > set_event clear_trace } fail() { #msg do_reset echo $1 exit $FAIL } if [ ! -f set_event -o ! -d events/sched ]; then echo "event tracing is not supported" exit_unsupported fi if [ ! -f events/sched/sched_process_fork/trigger ]; then echo "event trigger is not supported" exit_unsupported fi if [ ! -f events/sched/sched_process_fork/hist ]; then echo "hist trigger is not supported" exit_unsupported fi reset_tracer do_reset reset_trigger echo "Test histogram multiple tiggers" echo 'hist:keys=parent_pid:vals=child_pid' > events/sched/sched_process_fork/trigger echo 'hist:keys=parent_comm:vals=child_pid' >> events/sched/sched_process_fork/trigger for i in `seq 1 10` ; do ( echo "forked" > /dev/null); done grep parent_pid events/sched/sched_process_fork/hist > /dev/null || \ fail "hist trigger on sched_process_fork did not work" grep child events/sched/sched_process_fork/hist > /dev/null || \ fail "hist trigger on sched_process_fork did not work" COMM=`cat /proc/$$/comm` grep "parent_comm: $COMM" events/sched/sched_process_fork/hist > /dev/null || \ fail "string key on sched_process_fork did not work" reset_trigger echo "Test histogram with its name" echo 'hist:name=test_hist:keys=common_pid' > events/sched/sched_process_fork/trigger for i in `seq 1 10` ; do ( echo "forked" > /dev/null); done grep test_hist events/sched/sched_process_fork/hist > /dev/null || \ fail "named event on sched_process_fork did not work" echo "Test same named histogram on different events" echo 'hist:name=test_hist:keys=common_pid' > events/sched/sched_process_exit/trigger for i in `seq 1 10` ; do ( echo "forked" > /dev/null); done grep test_hist events/sched/sched_process_exit/hist > /dev/null || \ fail "named event on sched_process_fork did not work" diffs=`diff events/sched/sched_process_exit/hist events/sched/sched_process_fork/hist | wc -l` test $diffs -eq 0 || fail "Same name histograms are not same" reset_trigger do_reset exit 0 -next.git/diff/net/bridge/br_device.c?h=nds-private-remove&id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>diff
path: root/net/bridge/br_device.c
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-30 19:27:10 -0500
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-31 09:13:49 -0500
commit79c6f448c8b79c321e4a1f31f98194e4f6b6cae7 (patch)
tree370efda701f03cccf21e02bb1fdd3b852547d75c /net/bridge/br_device.c
parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (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 'net/bridge/br_device.c')