From: Luiz Capitulino <lcapitulino@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] QAPI conversion status and async commands support
Date: Mon, 12 Mar 2012 10:50:04 -0300 [thread overview]
Message-ID: <20120312105004.4a7e1f50@doriath.home> (raw)
In-Reply-To: <4F5DB72A.2080906@cn.fujitsu.com>
On Mon, 12 Mar 2012 16:43:22 +0800
Wen Congyang <wency@cn.fujitsu.com> wrote:
> > Having said that, I wonder if postponing want-to-be-async commands to 1.2 is
> > a good thing. Two solutions other than waiting:
> >
> > 1. Add synchronous versions of them, if possible (I think this is possible
> > for the dump command)
>
> I agree with this. libvirt uses migrate command to do dump now, and it cannot work
> when the guest uses host's device. We need to fix this bug as quickly as possible.
> So we need dump command recently. So I think we can add synchronous versions of
> dump command. Is it OK? If it is OK, I will send the synchronous versions of
> dump command.
I'd be fine with this because this command is expected to be used when the guest
crashes, right? In this case, I _guess_ that holding the global mutex for a long
time is not the end of the world, as the world has ended already :) Far from ideal,
of course, but is the best we can do right now.
Anthony, do you have objections?
next prev parent reply other threads:[~2012-03-12 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 16:36 [Qemu-devel] QAPI conversion status and async commands support Luiz Capitulino
2012-03-07 17:29 ` Paolo Bonzini
2012-03-07 17:36 ` Anthony Liguori
2012-03-07 18:12 ` Luiz Capitulino
2012-03-12 8:43 ` Wen Congyang
2012-03-12 13:50 ` Luiz Capitulino [this message]
2012-03-07 20:06 ` Alon Levy
2012-03-12 7:30 ` Alon Levy
2012-03-08 12:34 ` Kevin Wolf
2012-03-08 14:12 ` Paolo Bonzini
2012-03-08 14:22 ` Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120312105004.4a7e1f50@doriath.home \
--to=lcapitulino@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).