From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen watchdog improvements Date: Mon, 12 Aug 2013 16:20:37 +0100 Message-ID: <5208FD45.8010502@citrix.com> References: <1376314680-12548-1-git-send-email-andrew.cooper3@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7210114343576542075==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Josh Zhao Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org --===============7210114343576542075== Content-Type: multipart/alternative; boundary="------------090501020002050202010402" --------------090501020002050202010402 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 12/08/13 14:47, Josh Zhao wrote: > Hi Andrew, > What's the Watchdog used for in Xen? > > Josh Xen can set up a hardware watchdog on each pcpu, to help ensure that it doesn't get stuck in loops. It is extra defence against bugs in Xen. ~Andrew > > > 2013/8/12 Andrew Cooper > > > This series offers some improvements to Xen watchdogs. > > Patch 1 moves the concept of a watchdog from x86 specific code to > common. > Patch 2 tweaks the x86 implementation, given the common > implementation. > Patch 3 is a bugfix for certain cases where the watchdog code > interacts badly with > console_force_unlock(). > > Signed-off-by: Andrew Cooper > > CC: Keir Fraser > > CC: Jan Beulich > > CC: Tim Deegan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > > --------------090501020002050202010402 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit

On 12/08/13 14:47, Josh Zhao wrote:

Hi Andrew,
What's the Watchdog used for in Xen?

Josh

Xen can set up a hardware watchdog on each pcpu, to help ensure that it doesn't get stuck in loops. It is extra defence against bugs in Xen.

~Andrew

2013/8/12 Andrew Cooper <andrew.cooper3@citrix.com>

This series offers some improvements to Xen watchdogs.

Patch 1 moves the concept of a watchdog from x86 specific code to common.
Patch 2 tweaks the x86 implementation, given the common implementation.
Patch 3 is a bugfix for certain cases where the watchdog code interacts badly with
console_force_unlock().

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
CC: Keir Fraser <keir@xen.org>
CC: Jan Beulich <JBeulich@suse.com>
CC: Tim Deegan <tim@xen.org>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--------------090501020002050202010402-- --===============7210114343576542075== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============7210114343576542075==--