From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60775) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TtG8L-0006db-Of for qemu-devel@nongnu.org; Thu, 10 Jan 2013 06:17:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TtG8J-0007OQ-7Q for qemu-devel@nongnu.org; Thu, 10 Jan 2013 06:17:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:10898) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TtG8J-0007O6-10 for qemu-devel@nongnu.org; Thu, 10 Jan 2013 06:17:15 -0500 Message-ID: <50EEA334.6010105@redhat.com> Date: Thu, 10 Jan 2013 12:17:08 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <50EE8810.7080507@dlhnet.de> <8738y9l3ka.fsf@blackfin.pond.sub.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] block: init bs->io_base correctly to avoid locking List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: kwolf@redhat.com, Markus Armbruster , "qemu-devel@nongnu.org" Il 10/01/2013 11:59, Peter Lieven ha scritto: > I hope my fix is correct. Maybe there is sth else wrong, but at least this > fixes the locking of the guest for me. Yes, I also believe youre fix is correct (only aesthetic remarks). Paolo > My intention is not to limit I/O in general, just watch it and shape guests > that behave inappropriate.