From: Dave Jones <davej@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Cestonaro,
Thilo (external)" <Thilo.Cestonaro.external@fujitsu-siemens.com>,
Lee Revell <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org
Subject: Re: how can I touch softlockup watchdog on all cpus?
Date: Thu, 22 Mar 2007 21:16:17 -0400 [thread overview]
Message-ID: <20070323011617.GB1367@redhat.com> (raw)
In-Reply-To: <4603075E.4090001@goop.org>
On Thu, Mar 22, 2007 at 03:46:54PM -0700, Jeremy Fitzhardinge wrote:
> Cestonaro, Thilo (external) wrote:
> > It's a condition of a customer of us, so I can't change it.
> >
> > But it happens not often that my part is used. So I thought there is a mechanism to disable or reset the watchdog
> > because it is a legal pause for it. And there is one "touch_softlockup_watchdog()", that does what I want,
> > BUT just for the current cpu. And so the watchdog blats from the other cpu.
> >
>
> on_each_cpu(touch_softlockup_watchdog, NULL, 0, 0)?
He wants to do this with interrupts off. on_each_cpu won't work in
that situation.
> Or patch the softlockup watchdog to add a way to temporarily disable it.
Seems pretty much the only way you could make this work.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-03-23 1:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 16:06 how can I touch softlockup watchdog on all cpus? Cestonaro, Thilo (external)
2007-03-21 16:44 ` Dave Jones
2007-03-22 7:33 ` Cestonaro, Thilo (external)
2007-03-22 15:30 ` Lee Revell
2007-03-22 15:46 ` Cestonaro, Thilo (external)
2007-03-22 16:17 ` Lee Revell
2007-03-22 16:46 ` Cestonaro, Thilo (external)
2007-03-22 22:46 ` Jeremy Fitzhardinge
2007-03-23 1:16 ` Dave Jones [this message]
2007-03-23 1:48 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2007-03-21 16:10 Cestonaro, Thilo (external)
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=20070323011617.GB1367@redhat.com \
--to=davej@redhat.com \
--cc=Thilo.Cestonaro.external@fujitsu-siemens.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox