From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luiz Capitulino Subject: Re: [Qemu-devel] KVM call agenda for September 25th Date: Tue, 25 Sep 2012 10:27:50 -0300 Message-ID: <20120925102750.1d557bee@doriath.home> References: <87txunr76j.fsf@trasno.org> <5060488A.1050008@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: quintela@redhat.com, "Richard W.M. Jones" , qemu-devel , "kvm@vger.kernel.org" , Bharata B Rao To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:64904 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756237Ab2IYN1B (ORCPT ); Tue, 25 Sep 2012 09:27:01 -0400 In-Reply-To: <5060488A.1050008@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, 24 Sep 2012 13:48:26 +0200 Paolo Bonzini 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.