|
From: | Paolo Bonzini |
Subject: | Re: [Qemu-devel] [PATCH v4 01/15] coroutine: add co_sleep_ns() coroutine sleep function |
Date: | Thu, 12 Jan 2012 12:07:54 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0 |
On 01/12/2012 11:58 AM, Stefan Hajnoczi wrote:
This is something I'm looking at right now and will probably want to discuss with Paolo. In a coroutine we're probably using a main loop and timers should be available there. In general, the problem we're starting to see is that some block layer features are using timers (I/O throttling, QED deferred dirty bit clearing, image streaming). The question is do we isolate this functionality so it is unavailable from a qemu-tool world when there's no main loop, or do we move everything into a main loop?
Yes, I would move things into a main loop just like qemu-nbd does. I even had some prototype patches for it. The qemu-img part is broken because it uses callbacks that haven't been made asynchronous yet; the one for qemu-io should be okay modulo some more testing.
Paolo
tools-co.patch
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |