qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: [PATCH 01/11] QMP: Introduce specification file


From: Avi Kivity
Subject: Re: [Qemu-devel] Re: [PATCH 01/11] QMP: Introduce specification file
Date: Tue, 23 Jun 2009 18:01:32 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2

On 06/23/2009 04:40 PM, Anthony Liguori wrote:
IMO, there aren't any. All commands are synchronous (but may cause events to be generated later).


At least today, there are quite a few commands that are synchronous and block. They would all have to be converted to events. For instance:


That's what I meant, though I phrased it poorly.

commit

That's a biggie to make truly async.

change
screendump

I think we can keep those synchronous.

savevm
loadvm
delvm

Like commit, very difficult to make async.

stop
cont

These certainly seem very synchronous to me.

memsave
pmemsave

Can keep these synchronous IMO. You certainly don't want the guest to progress during memsave.

migrate
balloon

Isn't balloon synchronous? It sets the target and exits immediately. We don't want command completion to depend on the guest.

--

error compiling committee.c: too many arguments to function





reply via email to

[Prev in Thread] Current Thread [Next in Thread]