From: Jeremy Fitzhardinge <jeremy@goop.org> To: Andrew Morton <akpm@linux-foundation.org> Cc: Linux Kernel <linux-kernel@vger.kernel.org>, virtualization@lists.osdl.org, Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>, john stultz <johnstul@us.ibm.com> Subject: [patch 0/2] softlockup watchdog improvements Date: Mon, 26 Mar 2007 22:38:16 -0700 [thread overview] Message-ID: <20070327053816.881735237@goop.org> (raw) Here's couple of patches to improve the softlockup watchdog. The first changes the softlockup timer from using jiffies to sched_clock() as a timebase. Xen and VMI implement sched_clock() as counting unstolen time, so time stolen by the hypervisor won't cause the watchdog to bite. The second adds per-cpu enable flags for the watchdog timer. This allows the timer to be disabled when the CPU goes into a (potentially unbounded) tickless sleep. I know this conflicts with fix-bogus-softlockup-warning-with-sysrq-t.patch in -mm2. I think that patch incorrectly changes the behaviour of the softlockup watchdog, and a better solution is to temporarily disable the watchdog while doing something known to be cpu-consuming, like a long sysreq output. J --
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org> To: Andrew Morton <akpm@linux-foundation.org> Cc: virtualization@lists.osdl.org, Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>, Linux Kernel <linux-kernel@vger.kernel.org>, john stultz <johnstul@us.ibm.com> Subject: [patch 0/2] softlockup watchdog improvements Date: Mon, 26 Mar 2007 22:38:16 -0700 [thread overview] Message-ID: <20070327053816.881735237@goop.org> (raw) Here's couple of patches to improve the softlockup watchdog. The first changes the softlockup timer from using jiffies to sched_clock() as a timebase. Xen and VMI implement sched_clock() as counting unstolen time, so time stolen by the hypervisor won't cause the watchdog to bite. The second adds per-cpu enable flags for the watchdog timer. This allows the timer to be disabled when the CPU goes into a (potentially unbounded) tickless sleep. I know this conflicts with fix-bogus-softlockup-warning-with-sysrq-t.patch in -mm2. I think that patch incorrectly changes the behaviour of the softlockup watchdog, and a better solution is to temporarily disable the watchdog while doing something known to be cpu-consuming, like a long sysreq output. J --
next reply other threads:[~2007-03-27 5:48 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-27 5:38 Jeremy Fitzhardinge [this message] 2007-03-27 5:38 ` [patch 0/2] softlockup watchdog improvements Jeremy Fitzhardinge 2007-03-27 5:38 ` [patch 1/2] Ignore stolen time in the softlockup watchdog Jeremy Fitzhardinge 2007-03-27 7:00 ` Eric Dumazet 2007-03-27 7:12 ` Jeremy Fitzhardinge 2007-03-27 7:12 ` Jeremy Fitzhardinge 2007-03-27 7:50 ` Eric Dumazet 2007-03-27 7:50 ` Eric Dumazet 2007-03-27 14:39 ` Prarit Bhargava 2007-03-27 14:39 ` Prarit Bhargava 2007-03-27 16:37 ` Jeremy Fitzhardinge 2007-03-27 16:53 ` Prarit Bhargava 2007-03-27 16:53 ` Prarit Bhargava 2007-03-27 17:10 ` Jeremy Fitzhardinge 2007-03-27 17:10 ` Jeremy Fitzhardinge 2007-03-27 17:20 ` Prarit Bhargava 2007-03-27 17:20 ` Prarit Bhargava 2007-03-27 5:38 ` [patch 2/2] percpu enable flag for " Jeremy Fitzhardinge 2007-03-27 5:38 ` Jeremy Fitzhardinge 2007-03-27 14:42 ` Prarit Bhargava 2007-03-27 14:42 ` Prarit Bhargava
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=20070327053816.881735237@goop.org \ --to=jeremy@goop.org \ --cc=akpm@linux-foundation.org \ --cc=johnstul@us.ibm.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@elte.hu \ --cc=tglx@linutronix.de \ --cc=virtualization@lists.osdl.org \ /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: linkBe 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.