[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [RFC] [PATCH] One watchdog trips the watchdog on all processors


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: George Dunlap <dunlapg@xxxxxxxxx>
  • Date: Fri, 17 Jul 2009 13:55:16 +0100
  • Delivery-date: Fri, 17 Jul 2009 05:55:47 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=bRyU/34Z7JjAB+beUQ3glwfUSXb25SKBw4a6zvgGmf4D29W8YuzEPyjpq1ukNuAT96 yoCi4mpZLnOEPN8u5LK9VD/+DKQ5EVaptCPJLoyMmq/6xr8GAMBwGfMhjWbKbsjzM5Za KK/OSR2QUENsay8shBpM0wx7AgW2hxkmowoXk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I've been using the watchdog timer recently to debug deadlocks, and
found that it only triggers on one cpu.  Unfortunately, if your
deadlock is not symmetric, it's not often obvious what the other
cpu(s) is(are) doing.  The attached patch is a hack I put in place to
trigger an NMI on all cpus if it's triggered on one.  This will cause
things to hang instead of reboot, however, so I'm not sure how to
integrate it into the normal watchdog-for-reliability functionality
(as opposed to watchdog-for-debugging).

 -George

Attachment: watchdog-triggers-all-cpus.diff
Description: Text Data

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

 


Rackspace

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