From: Thomas Gleixner <tglx@linutronix.de>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Sebastian Sewior <bigeasy@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] hrtimer: Reset hrtimer cpu base proper on CPU hotplug
Date: Tue, 30 Jan 2018 22:03:17 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801302202510.2293@nanos> (raw)
In-Reply-To: <20180129234347.GA26365@linux.vnet.ibm.com>
On Mon, 29 Jan 2018, Paul E. McKenney wrote:
> On Mon, Jan 29, 2018 at 01:57:38AM -0800, Paul E. McKenney wrote:
> > On Mon, Jan 29, 2018 at 09:20:48AM +0100, Sebastian Sewior wrote:
> > > On 2018-01-26 14:09:17 [-0800], Paul E. McKenney wrote:
> > > > find this one. ;-) But it did pass rcutorture testing for a great many
> > > > years, didn't it? :-/
> > >
> > > It started to trigger better (or at all) on our test box with
> > > modprobe kvm_intel preemption_timer=n
> > >
> > > on the host kernel so maybe a completely unrelated change helped to
> > > trigger this.
> >
> > Good point!
> >
> > And testing continues, currently at 108 hours of TREE01 without any
> > waylayed timers, so looking good! ;-)
> >
> > Just kicked off another 70 hours worth.
>
> And those completed without incident for a total of 178 hours. I believe
> we can call this one fixed. Thank you all!!!
>
> One question... Is the patch shown below needed, or is this just yet
> another case of me being confused? (The lack of it is not triggering,
> but...)
See commit 26456f87aca7
next prev parent reply other threads:[~2018-01-30 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 13:54 [PATCH] hrtimer: Reset hrtimer cpu base proper on CPU hotplug Thomas Gleixner
2018-01-26 22:09 ` Paul E. McKenney
2018-01-28 0:53 ` Paul E. McKenney
2018-01-29 8:20 ` Sebastian Sewior
2018-01-29 9:57 ` Paul E. McKenney
2018-01-29 23:43 ` Paul E. McKenney
2018-01-30 21:03 ` Thomas Gleixner [this message]
2018-01-31 0:52 ` Paul E. McKenney
2018-01-27 14:31 ` [tip:timers/urgent] " tip-bot for Thomas Gleixner
2018-01-29 8:08 FAILED: patch "[PATCH] hrtimer: Reset hrtimer cpu base proper on CPU hotplug" failed to apply to 3.18-stable tree gregkh
2018-01-29 14:20 ` [PATCH] hrtimer: Reset hrtimer cpu base proper on CPU hotplug Sebastian Andrzej Siewior
2018-01-29 14:32 ` Greg KH
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=alpine.DEB.2.20.1801302202510.2293@nanos \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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.