From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1L00S3-0005Rq-BK
	for qemu-devel@nongnu.org; Tue, 11 Nov 2008 16:07:07 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1L00S1-0005QR-FI
	for qemu-devel@nongnu.org; Tue, 11 Nov 2008 16:07:06 -0500
Received: from [199.232.76.173] (port=56253 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1L00S1-0005QJ-BT
	for qemu-devel@nongnu.org; Tue, 11 Nov 2008 16:07:05 -0500
Received: from yw-out-1718.google.com ([74.125.46.156]:13241)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1L00S0-0006uF-Qh
	for qemu-devel@nongnu.org; Tue, 11 Nov 2008 16:07:04 -0500
Received: by yw-out-1718.google.com with SMTP id 6so42006ywa.82
	for <qemu-devel@nongnu.org>; Tue, 11 Nov 2008 13:07:04 -0800 (PST)
Message-ID: <4919F3F4.3010407@codemonkey.ws>
Date: Tue, 11 Nov 2008 15:07:00 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [patch] Fix block I/O hang.
References: <4919B46C.3040804@redhat.com>	<4919B79A.5030402@codemonkey.ws>	<4919C550.5020609@redhat.com>	<4919C71E.2030509@codemonkey.ws>
	<4919F062.2070504@redhat.com>
In-Reply-To: <4919F062.2070504@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Gerd Hoffmann wrote:
>
>>  However,
>>
>>     
>>> Third, when called from a select callback it shouldn't block indeed.  It
>>> does though for me now and then when booting xen guests (with a big
>>> stack of xenner patches).  Doesn't reproduce reliable though.  Sprinkled
>>> in a printk (with rfd being non-blocking) and got a EAGAIN once, so it
>>> got called with rfd not having data.
>>>       
>> I think it would be good to root cause this.  AFAICT, it shouldn't block.
>>     
>
> Yes, something is fishy here.  Will try to pin it.
> Ideas where to look are welcome in case you have any ;)
>   

Are you doing something funky with threads in xenner?

Regards,

Anthony Liguori

> cheers,
>   Gerd
>
>
>
>