From: Mike Galbraith <bitbucket@online.de>
To: Ethan Zhao <ethan.kernel@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rjw@sisk.pl, Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-pm@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH V3]hrtimer: Fix a performance regression by disable reprogramming in remove_hrtimer
Date: Thu, 12 Dec 2013 15:42:02 +0100 [thread overview]
Message-ID: <1386859322.6056.83.camel@marge.simpson.net> (raw)
In-Reply-To: <CABawtvNf5k8pKY6ioa8GdUzOn7h3aOBsWhSUNgmfuQSj+xtUbQ@mail.gmail.com>
On Thu, 2013-12-12 at 22:14 +0800, Ethan Zhao wrote:
> Mike,
> it seems the IPI issue got root cause (cpu hardware errata ) now ?
> I only catch some pieces of the mails, is that to say the crazy horse
> made by Intel will wake up unexpected, and eat too much reschedule
> IPI, then the horse got hotter, performance down, and so the fix would
> be a 'CFLUSH' to all the buggy CPU, is that right ?
You're mixing a couple different issues together, but yeah, close
enough. The barking amazonian tree guppy is being saved as we speak.
-Mike
prev parent reply other threads:[~2013-12-12 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130729115701.GD3008@twins.programming.kicks-ass.net>
[not found] ` <24EECBCC-F655-404F-8946-73CC36095A5F@gmail.com>
[not found] ` <1378362989.18435.2.camel@marge.simpson.net>
[not found] ` <20130905111428.GB23362@gmail.com>
[not found] ` <1378386697.6567.9.camel@marge.simpson.net>
[not found] ` <20130905133750.GA26637@gmail.com>
[not found] ` <1378445942.5434.31.camel@marge.simpson.net>
[not found] ` <20130909122325.GX31370@twins.programming.kicks-ass.net>
[not found] ` <1378730538.5586.30.camel@marge.simpson.net>
[not found] ` <20130909133044.GB31370@twins.programming.kicks-ass.net>
2013-09-09 13:46 ` [PATCH V3]hrtimer: Fix a performance regression by disable reprogramming in remove_hrtimer Peter Zijlstra
2013-09-11 8:56 ` Peter Zijlstra
2013-09-11 10:25 ` Mike Galbraith
2013-10-04 12:06 ` Ethan Zhao
2013-10-07 4:41 ` Mike Galbraith
2013-10-07 4:57 ` Ethan Zhao
2013-12-12 14:14 ` Ethan Zhao
2013-12-12 14:42 ` Mike Galbraith [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=1386859322.6056.83.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=daniel.lezcano@linaro.org \
--cc=ethan.kernel@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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