From: "Veijola, Erik" <erik.veijola@intel.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>, "bp@alien8.de" <bp@alien8.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] x86/mce: Make timer handling more robust
Date: Wed, 1 Feb 2017 09:29:22 +0000 [thread overview]
Message-ID: <1485941364.12475.5.camel@intel.com> (raw)
In-Reply-To: <20170131183749.32ol7i7qnjfa35qx@pd.tnic>
On Tue, 2017-01-31 at 19:37 +0100, Borislav Petkov wrote:
> Bah. That's wrong. Delta patch below:
> >
> > --- a/arch/x86/kernel/cpu/mcheck/mce.c
> > +++ b/arch/x86/kernel/cpu/mcheck/mce.c
> > @@ -1782,7 +1782,7 @@ static void mce_start_timer(struct timer
> > return;
> >
> > this_cpu_write(mce_next_interval, iv);
> > - __start_timer(t, jiffies + iv);
> > + __start_timer(t, iv);
> > }
> >
> > static void __mcheck_cpu_setup_timer(void)
>
> With that hunk merged in:
>
> Reviewed-by: Borislav Petkov <bp@suse.de>
> Tested-by: Borislav Petkov <bp@suse.de>
>
> Thanks!
>
Tested this on the preproduction hardware:
Tested-by: Erik Veijola <erik.veijola@intel.com>
-Erik
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2017-02-01 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 8:37 [PATCH] x86/mce: Make timer handling more robust Thomas Gleixner
2017-01-31 13:33 ` Thomas Gleixner
2017-01-31 18:37 ` Borislav Petkov
2017-02-01 9:29 ` Veijola, Erik [this message]
2017-01-31 18:36 ` Borislav Petkov
2017-01-31 20:51 ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
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=1485941364.12475.5.camel@intel.com \
--to=erik.veijola@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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