From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: "xm save" trouble -- deadlock? Date: Wed, 02 Nov 2005 12:24:59 +0100 Message-ID: <4368A20B.2090106@suse.de> References: <43679B4C.3030804@suse.de> <4367A2AF.2090707@suse.de> <20051101185456.GA21507@leeni.uk.xensource.com> <43688610.2010601@suse.de> <20051102100429.GA408@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051102100429.GA408@leeni.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: xen-devel List-Id: xen-devel@lists.xenproject.org > I've done a threaded fix already. You're welcome to have a go at doing it > without a thread if you want, but I think it'll be messy. Looks like, yes. Mixing the high-level buffered file I/O together with select() (and non-blocking fd's) usually doesn't work out very well. Going down using os.read() instead likely makes the code more complex than using one thread per file descriptor ... cheers, Gerd