[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [Qemu-devel] [PATCH for-2.9 5/5] coroutine: Explicitly
|
From: |
Fam Zheng |
|
Subject: |
Re: [Qemu-block] [Qemu-devel] [PATCH for-2.9 5/5] coroutine: Explicitly specify AioContext when creating coroutine |
|
Date: |
Fri, 7 Apr 2017 16:34:24 +0800 |
|
User-agent: |
Mutt/1.8.0 (2017-02-23) |
On Thu, 04/06 18:20, Kevin Wolf wrote:
> For example, another case where this happens is that block jobs follow
> their nodes if the AioContext changes and even implement
> .attached_aio_context callbacks when they need to drag additional nodes
> into the new context. With your change, the job coroutine would remember
> the old coroutine and move back to the old context in some cases!
You are right, in v2 I'll store the co->ctx at enter time explicitly. This way a
context change on a BDS will also move the block job's co.
Fam
- Re: [Qemu-block] [PATCH for-2.9 3/5] block: Quiesce old aio context during bdrv_set_aio_context, (continued)
[Qemu-block] [PATCH for-2.9 4/5] block: Drain BH in bdrv_drained_begin, Fam Zheng, 2017/04/06
[Qemu-block] [PATCH for-2.9 5/5] coroutine: Explicitly specify AioContext when creating coroutine, Fam Zheng, 2017/04/06