summaryrefslogtreecommitdiff
path: root/taia.c
diff options
context:
space:
mode:
authorVadim Kochan <vadim4j@gmail.com>2015-10-24 17:38:08 +0300
committerTobias Klauser <tklauser@distanz.ch>2015-10-26 13:29:20 +0100
commitecfd9fb37218c6a2433074432b6dfa1ef2ca392e (patch)
tree298b05d8ca4bffa101f0aeb8f8f1e306f81f7eff /taia.c
parente97a3b2a56efdb1833c6f1228f50b2636977647e (diff)
flowtop: man: Add notice about rate info
Add notice about rate info to the feature list. Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'taia.c')
0 files changed, 0 insertions, 0 deletions
&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 'drivers/usb/host/ohci-mem.c')