From: Peter Zijlstra <peterz@infradead.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
"Deng, Dongdong" <Dongdong.Deng@windriver.com>
Subject: Re: [PATCH] softlockup: fix problem with long kernel pauses from kgdb
Date: Mon, 27 Jul 2009 22:18:13 +0200 [thread overview]
Message-ID: <1248725893.6987.2055.camel@twins> (raw)
In-Reply-To: <4A6E0825.3020604@windriver.com>
On Mon, 2009-07-27 at 15:03 -0500, Jason Wessel wrote:
>
> The fix is to simply invoke sched_clock_tick() to update "cpu sched
> clock" on exit from kgdb_handle_exception.
Is that a regular IRQ context, or is that NMI context?
> Signed-off-by: Dongdong Deng <Dongdong.Deng@windriver.com>
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: peterz@infradead.org
> ---
> kernel/softlockup.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> --- a/kernel/softlockup.c
> +++ b/kernel/softlockup.c
> @@ -118,6 +118,9 @@ void softlockup_tick(void)
> }
>
> if (touch_timestamp == 0) {
> + /* If the time stamp was touched externally make sure the
> + * scheduler tick is up to date as well */
> + sched_clock_tick();
> __touch_softlockup_watchdog();
> return;
> }
>
Aside from the funny comment style (please fix) the fix does look
sensible.
next prev parent reply other threads:[~2009-07-27 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 20:03 [PATCH] softlockup: fix problem with long kernel pauses from kgdb Jason Wessel
2009-07-27 20:18 ` Peter Zijlstra [this message]
2009-07-27 21:25 ` Jason Wessel
2009-07-28 15:05 ` Jason Wessel
2009-08-04 14:16 ` Ingo Molnar
2009-08-04 14:53 ` [PATCH] softlockup: fix problem with long kernel pauses fromkgdb Jason Wessel
2009-08-04 14:59 ` Ingo Molnar
2009-08-21 12:42 ` [PATCH] softlockup: fix problem with long kernel pauses from kgdb DDD
2009-09-26 3:01 ` Yong Zhang
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=1248725893.6987.2055.camel@twins \
--to=peterz@infradead.org \
--cc=Dongdong.Deng@windriver.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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