All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Glauber de Oliveira Costa <gcosta@redhat.com>,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH] Avoid triggering the softlockup BUG when offline for too long.
Date: Wed, 29 Nov 2006 12:18:12 +0000	[thread overview]
Message-ID: <C1932B04.5382%keir@xensource.com> (raw)
In-Reply-To: <20061129120859.GB23434@redhat.com>

On 29/11/06 12:08, "Glauber de Oliveira Costa" <gcosta@redhat.com> wrote:

> [LINUX] Avoid triggering the softlockup BUG when offline for too long.
> 
> After being offline for a long time, the softlockup  watchdog triggers
> a BUG() on our faces. This is expected, as in fact, we spent more than
> a fixed 10*HZ amount of time without touching the watchdog.
> 
> However, by inspecting the contents of stolen inside timer irq handler,
> we can gain awareness of the fact, and do better than that.
> This patch fixes it.

Thanks. I changed the threshold to 5*HZ just to avoid marginal cases where
we might be offlined for just less than 10 seconds, and then if the per-cpu
watchdog process hasn't run for a second or two before we were offlined then
that would push us over the edge to print a warning. 5*HZ is much more
comfortable.

 -- Keir

  reply	other threads:[~2006-11-29 12:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 12:08 [PATCH] Avoid triggering the softlockup BUG when offline for too long Glauber de Oliveira Costa
2006-11-29 12:18 ` Keir Fraser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-24 13:10 Glauber de Oliveira Costa
2006-11-27 10:21 ` Keir Fraser
2006-11-27 15:31   ` Glauber de Oliveira Costa
2006-11-27 16:47     ` Glauber de Oliveira Costa
2006-11-27 18:54       ` Keir Fraser
2006-11-29 11:46         ` Glauber de Oliveira Costa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C1932B04.5382%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=gcosta@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.