From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: NMI: Enable watchdog by default Date: Wed, 07 Mar 2012 17:41:55 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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: George Dunlap Cc: Andrew Cooper , "xen-devel@lists.xensource.com" , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 07/03/2012 17:35, "George Dunlap" wrote: > On Wed, Mar 7, 2012 at 5:11 PM, Keir Fraser wrote: >> On 07/03/2012 16:55, "Andrew Cooper" wrote: >> = >>> This patch is based on one which has been in XenServer for a very long. >>> = >>> To keep the trend of documentation going, it also corrects the new >>> command line document. >> = >> This does not only enable the watchdog by default, but also changes the >> timeout from 5 seconds to 5 *minutes*! >> = >> Even if that is a good idea in some cases, we'd at least have to make the >> timeout configurable. Developers will not appreciate having to wait for 5 >> minutes for their lockups to produce useful trace output. > = > Yes, the 5 minute timeout is what we ship for production boxes, so > that we can catch actual deadlocks while being *really really* sure we > don't take down a customer's system unless it's *really* dead. I > think leaving the timeout as it is and making it configurable is > probably the best option. A patch to do that would be acceptable. With that we may as well keep NMI watchdog disabled by default, and default timeout of 5 seconds. That then means that XenServer carries a command-line option for its watchdog settings, rather than a patch. -- Keir > -George > = >> = >> =A0-- Keir >> = >> = >> = >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel