diff options
author | 2012-10-26 23:03:49 +0900 | |
---|---|---|
committer | 2012-12-01 16:45:45 -0800 | |
commit | 3657600040a7279e52252af3f9d7e253f4f49ef0 (patch) | |
tree | 1cc95124c9108e24ee18a7d9af2e511fd735daae /tools/perf/scripts/python/export-to-postgresql.py | |
parent | workqueue: trivial fix for return statement in work_busy() (diff) | |
download | linux-dev-3657600040a7279e52252af3f9d7e253f4f49ef0.tar.xz linux-dev-3657600040a7279e52252af3f9d7e253f4f49ef0.zip |
workqueue: add WARN_ON_ONCE() on CPU number to wq_worker_waking_up()
Recently, workqueue code has gone through some changes and we found
some bugs related to concurrency management operations happening on
the wrong CPU. When a worker is concurrency managed
(!WORKER_NOT_RUNNIG), it should be bound to its associated cpu and
woken up to that cpu. Add WARN_ON_ONCE() to verify this.
Signed-off-by: Joonsoo Kim <js1304@gmail.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions