From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Don Zickus <dzickus@redhat.com>,
fweisbec@gmail.com, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] watchdog: touch_nmi_watchdog should only touch local cpu not every one
Date: Fri, 5 Nov 2010 12:58:55 -0700 [thread overview]
Message-ID: <20101105125855.20e5ce4c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101105135117.GA27712@swordfish.minsk.epam.com>
On Fri, 5 Nov 2010 15:51:18 +0200
Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> On (11/04/10 21:18), Don Zickus wrote:
> > void touch_nmi_watchdog(void)
> > {
> > + /*
> > + * Using __raw here because some code paths have
> > + * preemption enabled. If preemption is enabled
> > + * then interrupts should be enabled too, in which
> > + * case we shouldn't have to worry about the watchdog
> > + * going off.
> > + */
> > + __raw_get_cpu_var(watchdog_nmi_touch) = true;
> > +
> > + touch_softlockup_watchdog();
> > +}
> > +EXPORT_SYMBOL(touch_nmi_watchdog);
> > +
> > +void touch_all_nmi_watchdogs(void)
> > +{
> > if (watchdog_enabled) {
> > unsigned cpu;
> >
> > @@ -151,7 +166,7 @@ void touch_nmi_watchdog(void)
> > }
> > touch_softlockup_watchdog();
> > }
> > -EXPORT_SYMBOL(touch_nmi_watchdog);
> > +EXPORT_SYMBOL(touch_all_nmi_watchdogs);
> >
>
> Hello,
> Seems like no one is actually calling touch_all_nmi_watchdogs, as for now.
> Right?
Yes, there doesn't seem a lot of point in adding the interface unless
we have callers.
>
> Minor nit
>
> touch_all_nmi_watchdogs:
> ...
> for_each_present_cpu(cpu) {
> if (per_cpu(watchdog_nmi_touch, cpu) != true)
> per_cpu(watchdog_nmi_touch, cpu) = true;
> }
>
>
> which is, I belive, could be simplified to
> for_each_present_cpu(cpu) {
> per_cpu(watchdog_nmi_touch, cpu) = true;
> }
We sometimes do this trick to avoid dirtying lots of cachelines which
already held the correct value. It'll be extra-benefical when dealing
with other CPU's data, I expect.
next prev parent reply other threads:[~2010-11-05 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 1:18 [PATCH] watchdog: touch_nmi_watchdog should only touch local cpu not every one Don Zickus
2010-11-05 13:51 ` Sergey Senozhatsky
2010-11-05 19:58 ` Andrew Morton [this message]
2010-11-08 13:37 ` Don Zickus
2010-11-07 22:09 ` Frederic Weisbecker
2010-11-08 13:38 ` Don Zickus
-- strict thread matches above, loose matches on Subject: below --
2013-12-05 3:12 [PATCH v2] watchdog: Add a sysctl to disable soft lockup detector Don Zickus
2013-12-05 20:42 ` [PATCH] watchdog: touch_nmi_watchdog should only touch local cpu not every one Ben Zhang
2013-12-16 15:55 ` Don Zickus
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=20101105125855.20e5ce4c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sergey.senozhatsky@gmail.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