From: "Zhou, Libing (NSB - CN/Hangzhou)" <libing.zhou@nokia-sbell.com>
To: "peterz@infradead.org" <peterz@infradead.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "bp@suse.de" <bp@suse.de>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>
Subject: RE: [PATCH] x86/nmi: Fix nmi_handle duration miscalculation
Date: Thu, 20 Aug 2020 02:31:45 +0000 [thread overview]
Message-ID: <c3a422ace0724f1f986b4fc033fa065f@nokia-sbell.com> (raw)
In-Reply-To: <20200819080645.GX2674@hirez.programming.kicks-ass.net>
Thanks for your comments, I will recommit patch soon.
-----Original Message-----
From: peterz@infradead.org <peterz@infradead.org>
Sent: 2020年8月19日 16:07
To: Zhou, Libing (NSB - CN/Hangzhou) <libing.zhou@nokia-sbell.com>
Cc: tglx@linutronix.de; mingo@redhat.com; bp@alien8.de; bp@suse.de; x86@kernel.org; linux-kernel@vger.kernel.org; hpa@zytor.com
Subject: Re: [PATCH] x86/nmi: Fix nmi_handle duration miscalculation
On Mon, Aug 17, 2020 at 05:04:41PM +0800, Libing Zhou wrote:
> In nmi_check_duration(), the 'whole_msecs' value should get from
> 'duration' to reflect actual time duration, but not
> 'action->max_duration'.
Fixes: 248ed51048c4 ("x86/nmi: Remove irq_work from the long duration NMI handler")
> Signed-off-by: Libing Zhou <libing.zhou@nokia-sbell.com>
> ---
> arch/x86/kernel/nmi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c index
> 4fc9954a9560..c51ee659e520 100644
> --- a/arch/x86/kernel/nmi.c
> +++ b/arch/x86/kernel/nmi.c
> @@ -102,7 +102,7 @@ fs_initcall(nmi_warning_debugfs);
>
> static void nmi_check_duration(struct nmiaction *action, u64
> duration) {
> - u64 whole_msecs = READ_ONCE(action->max_duration);
> + u64 whole_msecs = duration;
> int remainder_ns, decimal_msecs;
>
> if (duration < nmi_longest_ns || duration < action->max_duration)
The, IMO, saner solution is:
---
diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c index 4fc9954a9560..47381666d6a5 100644
--- a/arch/x86/kernel/nmi.c
+++ b/arch/x86/kernel/nmi.c
@@ -102,7 +102,6 @@ fs_initcall(nmi_warning_debugfs);
static void nmi_check_duration(struct nmiaction *action, u64 duration) {
- u64 whole_msecs = READ_ONCE(action->max_duration);
int remainder_ns, decimal_msecs;
if (duration < nmi_longest_ns || duration < action->max_duration) @@ -110,12 +109,12 @@ static void nmi_check_duration(struct nmiaction *action, u64 duration)
action->max_duration = duration;
- remainder_ns = do_div(whole_msecs, (1000 * 1000));
+ remainder_ns = do_div(duration, (1000 * 1000));
decimal_msecs = remainder_ns / 1000;
printk_ratelimited(KERN_INFO
"INFO: NMI handler (%ps) took too long to run: %lld.%03d msecs\n",
- action->handler, whole_msecs, decimal_msecs);
+ action->handler, duration, decimal_msecs);
}
static int nmi_handle(unsigned int type, struct pt_regs *regs)
prev parent reply other threads:[~2020-08-20 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 9:04 Libing Zhou
2020-08-19 8:06 ` peterz
2020-08-20 2:31 ` Zhou, Libing (NSB - CN/Hangzhou) [this message]
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=c3a422ace0724f1f986b4fc033fa065f@nokia-sbell.com \
--to=libing.zhou@nokia-sbell.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®