From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, Marcos Oviedo <moviedo.maillist@gmail.com>,
Markus Armbruster <armbru@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] monitor: Add force option support to pci_del command
Date: Thu, 17 Jun 2010 13:20:30 -0500 [thread overview]
Message-ID: <4C1A676E.5030002@codemonkey.ws> (raw)
In-Reply-To: <20100617151543.562ba3e1@redhat.com>
On 06/17/2010 01:15 PM, Luiz Capitulino wrote:
> This is a general question for all commands that can take way too long
> or never return.
>
> For QMP the question is whether we should handle this in QEMU or in the
> client. Ie, if the guest doesn't respond the client could detect that
> and cancel the async command.
>
Exactly. It's no different than a migration that takes too long.
> For HMP we could just live with that or suspend the shell and allow the
> user to cancel the operation (eg. ctrl+c) and the obvious alternative is to
> have timeouts, allowing the user to set them.
>
Yeah, ctrl+c to cancel would be a very nice feature.
Regards,
Anthony Liguori
prev parent reply other threads:[~2010-06-17 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 5:37 [Qemu-devel] [PATCH] monitor: Add force option support to pci_del command Marcos Oviedo
2010-06-09 6:39 ` Markus Armbruster
2010-06-09 7:38 ` Gerd Hoffmann
2010-06-09 14:00 ` Marcos Oviedo
2010-06-09 14:27 ` Gerd Hoffmann
2010-06-14 16:59 ` Anthony Liguori
2010-06-15 8:46 ` Gerd Hoffmann
2010-06-15 9:03 ` Markus Armbruster
2010-06-17 18:15 ` Luiz Capitulino
2010-06-17 18:20 ` Anthony Liguori [this message]
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=4C1A676E.5030002@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=moviedo.maillist@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).