From: Don Zickus <dzickus@redhat.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Mandeep Singh Baines <msb@chromium.org>
Subject: Re: [PATCH] watchdog: make sure the watchdog thread gets CPU on loaded system
Date: Tue, 13 Mar 2012 09:42:24 -0400 [thread overview]
Message-ID: <20120313134224.GU24378@redhat.com> (raw)
In-Reply-To: <1331631922-10466-1-git-send-email-mhocko@suse.cz>
On Tue, Mar 13, 2012 at 10:45:22AM +0100, Michal Hocko wrote:
> If the system is loaded while hotplugging a CPU we might end up with a bogus
> hardlockup detection. This has been seen during LTP pounder test executed
> in parallel with hotplug test.
>
> The main problem is that enable_watchdog (called when CPU is brought up)
> registers perf event which periodically checks per-cpu counter
> (hrtimer_interrupts), updated from a hrtimer callback, but the hrtimer is fired
> from the kernel thread.
Seems reasonable to me. I'll apply it.
Thanks,
Don
next prev parent reply other threads:[~2012-03-13 13:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 9:45 [PATCH] watchdog: make sure the watchdog thread gets CPU on loaded system Michal Hocko
2012-03-13 13:42 ` Don Zickus [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-14 20:38 [PATCH] watchdog: Make " Don Zickus
2012-03-14 20:59 ` Mandeep Singh Baines
2012-03-14 23:19 ` Andrew Morton
2012-03-15 1:45 ` Mandeep Singh Baines
2012-03-15 11:00 ` Peter Zijlstra
2012-03-15 11:06 ` Peter Zijlstra
2012-03-15 12:42 ` Ingo Molnar
2012-03-15 14:00 ` Peter Zijlstra
2012-03-15 14:35 ` Don Zickus
2012-03-15 15:39 ` Mandeep Singh Baines
2012-03-15 16:10 ` Peter Zijlstra
2012-03-15 16:11 ` Peter Zijlstra
2012-03-15 16:16 ` Peter Zijlstra
2012-03-15 17:04 ` Mandeep Singh Baines
2012-03-15 8:02 ` Michal Hocko
2012-03-15 15:54 ` Don Zickus
2012-03-15 16:04 ` Peter Zijlstra
2012-03-19 22:00 ` Andrew Morton
2012-03-15 16:14 ` Michal Hocko
2012-03-15 17:14 ` 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=20120313134224.GU24378@redhat.com \
--to=dzickus@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mingo@elte.hu \
--cc=msb@chromium.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: 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.