 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] [RFC] [PATCH] One watchdog trips the watchdog on all process
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] [RFC] [PATCH] One watchdog trips the watchdog on all processors |
| From: | George Dunlap <dunlapg@xxxxxxxxx> |
| Date: | Fri, 17 Jul 2009 13:55:16 +0100 |
| Delivery-date: | Fri, 17 Jul 2009 05:55:47 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=cEqXJkejOsZ5T3t1eqMpIhg6O2qHU40SaEbjT+tNvCI=; b=q5gDm0RfuYBOVIF1eUIXJLErl0GyrcpsPgO30ro5iJXyiEHj9GjkdvZOiLh35sA3fU 9axd5wRwrT2GCyecF6Za6giAoyRTyf/ekFoEokyxdKWF20HOW3FVsAvyFZumCG4ACzwt h24DMd2g4LxcPKNKx5ZcpcjGv6hSWhj6F/B94= |
| 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= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] 2.6.30 dom0 Xen patches, Pasi Kärkkäinen |
|---|---|
| Next by Date: | Re: [Xen-devel] 2.6.30 dom0 Xen patches, Boris Derzhavets |
| Previous by Thread: | [Xen-devel] [PATCH] x86: moke show_page_walk() more robust, Jan Beulich |
| Next by Thread: | Re: [Xen-devel] [RFC] [PATCH] One watchdog trips the watchdog on allprocessors, Jan Beulich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
