[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] "xm save" trouble -- deadlock?

  • To: Gerd Knorr <kraxel@xxxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Wed, 2 Nov 2005 10:28:30 -0800
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>
  • Delivery-date: Wed, 02 Nov 2005 18:25:35 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=nHaPpxa3ReuQxLWtmVIH8OOl/HOFKwFNrHeBrHh+/+Cg0ekorKa93w9GSN1AOz1Rv0BeN07IAHZtG+txYA8zReMZun6mBH9i/oyK1NEP0Fz3i/pLDisfJilipiinlZbHpY691vbP0jpPtFCwPhpjDIzwFTJ8VC8F/L9v3bbyz18=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>



What exactly is the thread shutdown problem here?  Why the timeout is
needed in the first place?

I didn't see an answer on this thread so I'll take a stab.

If you do a select without a timeout and no activity occurs on the file descriptors the thread may have no way of exiting cleanly.

     -Kip
 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.