summaryrefslogtreecommitdiff
path: root/oui.conf
diff options
context:
space:
mode:
authorJaroslav Škarvada <jskarvad@redhat.com>2017-07-03 18:24:32 +0200
committerTobias Klauser <tobias.klauser@gmail.com>2017-07-04 10:09:09 +0200
commit551aa0ee996132e443b5d12cbb6f114ac9aabcd3 (patch)
tree582a4ea7edf5ead98f1fe16674b396461208e884 /oui.conf
parent3f6b67be759be729100b54cc26462d7ae0107dfa (diff)
staging: compilation fix with new gcc
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
Diffstat (limited to 'oui.conf')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 15:45:17 +0000
f77d72b3dcebb7a8f2684633ec79be88'>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 'sound/soc/samsung/s3c-i2s-v2.h')