From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:45597) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TtFET-00012w-8d for qemu-devel@nongnu.org; Thu, 10 Jan 2013 05:19:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TtFEP-00084k-3y for qemu-devel@nongnu.org; Thu, 10 Jan 2013 05:19:33 -0500 Received: from mx1.redhat.com ([209.132.183.28]:17602) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TtFEO-00083m-SJ for qemu-devel@nongnu.org; Thu, 10 Jan 2013 05:19:29 -0500 Message-ID: <50EE95AA.4010904@redhat.com> Date: Thu, 10 Jan 2013 11:19:22 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <50EE8810.7080507@dlhnet.de> In-Reply-To: <50EE8810.7080507@dlhnet.de> 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, "qemu-devel@nongnu.org" Il 10/01/2013 10:21, Peter Lieven ha scritto: > If io_limits are specified during runtime that exceed the number of > operations in flight > bs->io_base is not initialized in the else statement in > bdrv_exceed_io_limits(). > The wait time calculated in bdrv_exceed_{bps,iops}_limits is thus > totally wrong > and the machine locks. > > Signed-off-by: Peter Lieven > --- > block.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/block.c b/block.c > index 4e28c55..309aa85 100644 > --- a/block.c > +++ b/block.c > @@ -159,6 +159,10 @@ void bdrv_io_limits_enable(BlockDriverState *bs) > bs->slice_start = qemu_get_clock_ns(vm_clock); > bs->slice_end = bs->slice_start + bs->slice_time; > memset(&bs->io_base, 0, sizeof(bs->io_base)); Please remove this memset. > + bs->io_base.bytes[0] = bs->nr_bytes[0]; > + bs->io_base.bytes[1] = bs->nr_bytes[1]; > + bs->io_base.ios[0] = bs->nr_ops[0]; > + bs->io_base.ios[1] = bs->nr_ops[1]; > bs->io_limits_enabled = true; > } > Also, perhaps you can just call bdrv_exceed_io_limits(bs, 0, 0, NULL); (which also subsumes the setting of slice_time, slice_start, slice_end). Paolo