From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: [PATCH] libxl: Use xenbus to communicate with xenstore if the socket fails Date: Thu, 9 Dec 2010 10:53:51 +0000 Message-ID: <4D00B53F.2020903@eu.citrix.com> References: <1291886276.13966.4612.camel@zakaz.uk.xensource.com> <4D00AA19.30205@eu.citrix.com> <1291890116.13966.4619.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1291890116.13966.4619.camel@zakaz.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: Ian Campbell Cc: Mihir Nanavati , xen-devel List-Id: xen-devel@lists.xenproject.org On 09/12/10 10:21, Ian Campbell wrote: >> I think there was at least 1 other practical differences, but it >> seems to have eluded me. Thinking more about it, it might be related to timeout, and/or it might be: If xenstored has decided to not answer you, your thread is dead in the water, because you end up stuck in kernel land forever (wait not interruptible aka D). (It might have been related to historical reasons, however it could still be happening in the unlikely event of xenstored dying) -- Vincent