From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for September 25th
Date: Tue, 25 Sep 2012 10:27:50 -0300 [thread overview]
Message-ID: <20120925102750.1d557bee@doriath.home> (raw)
In-Reply-To: <5060488A.1050008@redhat.com>
On Mon, 24 Sep 2012 13:48:26 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 24/09/2012 13:28, Juan Quintela ha scritto:
> > Hi
> >
> > Please send in any agenda items you are interested in covering.
>
> URI parsing library for glusterfs: libxml2 vs. in-tree "fork" of the
> same code.
Case we're going to have the call (otherwise let's discuss it on the
list):
- change blocking I/O to non-blocking I/O for qmp commands?
We have a few qmp commands that do blocking I/O (eg. screendump and
dump-guest-memory). Theoretically, those commands could block forever.
This is a more serious issue with the screendump command, which doesn't
stop vcpus.
I've never received a report about this, so maybe this is not an issue.
But, while the perfect solution here is to have async commands, I was
wondering if it would be feasible for synchronous commands like screendump
to be changed to use non-blocking fds. This way we don't risk blocking.
prev parent reply other threads:[~2012-09-25 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 11:28 [Qemu-devel] KVM call agenda for September 25th Juan Quintela
2012-09-24 11:48 ` Paolo Bonzini
2012-09-25 12:13 ` Richard W.M. Jones
2012-09-25 12:57 ` Anthony Liguori
2012-09-25 13:05 ` Richard W.M. Jones
2012-09-25 13:14 ` Luiz Capitulino
2012-09-25 13:30 ` Paolo Bonzini
2012-09-25 14:51 ` Kevin Wolf
2012-09-25 15:33 ` Bharata B Rao
2012-09-25 15:37 ` Paolo Bonzini
2012-09-25 19:42 ` Anthony Liguori
2012-09-26 7:10 ` Markus Armbruster
2012-09-25 13:27 ` Luiz Capitulino [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=20120925102750.1d557bee@doriath.home \
--to=lcapitulino@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rjones@redhat.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).