| commit | 0ffbce80c263821161190f20e74a12f7aa8eab7b | [log] [tgz] |
|---|---|---|
| author | Jens Axboe <axboe@fb.com> | Wed Jun 25 08:22:34 2014 -0600 |
| committer | Jens Axboe <axboe@fb.com> | Wed Jun 25 08:22:34 2014 -0600 |
| tree | 870368a850b6ebb37e30c3d4407649f30f2d4741 | |
| parent | 66cb45aa41315d1d9972cada354fbdf7870d7714 [diff] |
blk-mq: blk_mq_start_hw_queue() should use blk_mq_run_hw_queue() Currently it calls __blk_mq_run_hw_queue(), which depends on the CPU placement being correct. This means it's not possible to call blk_mq_start_hw_queues(q) from a context that is correct for all queues, leading to triggering the WARN_ON(!cpumask_test_cpu(raw_smp_processor_id(), hctx->cpumask)); in __blk_mq_run_hw_queue(). Reported-by: Ming Lei <tom.leiming@gmail.com> Signed-off-by: Jens Axboe <axboe@fb.com>