From: Alex Shi <alex.shi@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Davidlohr Bueso <davidlohr.bueso@hp.com>,
hpa@linux.intel.com, tim.c.chen@linux.intel.com,
linux-kernel@vger.kernel.org, andi.kleen@intel.com,
a.p.zijlstra@chello.nl, mingo@elte.hu
Subject: Re: [URGENT rfc patch 0/3] tsc clocksource bug fix
Date: Fri, 05 Jul 2013 09:12:55 +0800 [thread overview]
Message-ID: <51D61D97.8060904@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1307042214090.11637@ionos.tec.linutronix.de>
On 07/05/2013 04:27 AM, Thomas Gleixner wrote:
>>>> We find some benchmarks drop a lot on tip/sched/core on many Intel boxes,
> And that branch does NOT have that commit included. So how can you see
> a regression on a branch caused by a commit NOT included into that
> branch?
>
> The offending commit is in tip timers/core and not in tip
> sched/core. What I'm wanted to say is, that we need a proper
> description of problems and not some random association.
>
> It tricked you to assume, that I'm not able to figure it out myself :)
>
> See? These things are complex and subtle, so we need precise
> descriptions and not some sloppy semi correct data.
>
> I'm well aware of the issue and with Peters help I got a reasonable
> explanation for it. A proper fix is about to be sent out.
>
Ingo had merged your branch into sched/core. :)
commit f9bed7021710a3e45c331f7d7781de914cc1b939
Merge: 7e76057 67dd331
Author: Ingo Molnar <mingo@kernel.org>
Date: Wed May 29 11:21:59 2013 +0200
Merge branch 'timers/urgent'
...
commit 7d194f78bde64ec813c1ed8291181bdd61515e78
Merge: 0298bf7 1eaff67
Author: Ingo Molnar <mingo@kernel.org>
Date: Tue May 28 09:53:41 2013 +0200
Merge branch 'timers/core'
commit 0298bf70644d7334bec16ae47f3aa58f4f883b59
Merge: cc662fa 2938d27
Author: Ingo Molnar <mingo@kernel.org>
Date: Tue May 28 09:49:51 2013 +0200
Merge branch 'timers/urgent'
--
Thanks
Alex
next prev parent reply other threads:[~2013-07-05 1:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 5:34 [URGENT rfc patch 0/3] tsc clocksource bug fix Alex Shi
2013-07-04 5:34 ` [PATCH 1/3] clocksource: clean up clocksource_select Alex Shi
2013-07-04 9:57 ` Thomas Gleixner
2013-07-04 10:21 ` Alex Shi
2013-07-04 10:27 ` Thomas Gleixner
2013-07-05 1:22 ` Alex Shi
2013-07-04 5:34 ` [PATCH 2/3] clockesource: set override clocksource Alex Shi
2013-07-04 10:23 ` Thomas Gleixner
2013-07-04 5:34 ` [PATCH 3/3] clocksource: fix can not set tsc as clocksource bug Alex Shi
2013-07-04 10:55 ` Thomas Gleixner
2013-07-04 13:04 ` Thomas Gleixner
2013-07-04 20:46 ` [PATCH] clocksource: Reselect clocksource when watchdog validated Thomas Gleixner
2013-07-05 1:38 ` Alex Shi
2013-07-05 9:13 ` [tip:timers/core] clocksource: Reselect clocksource when watchdog validated high-res capability tip-bot for Thomas Gleixner
2013-07-05 2:48 ` [PATCH 3/3] clocksource: fix can not set tsc as clocksource bug Alex Shi
2013-07-05 5:41 ` Thomas Gleixner
2013-07-05 6:44 ` Alex Shi
2013-07-04 7:58 ` [URGENT rfc patch 0/3] tsc clocksource bug fix Peter Zijlstra
2013-07-04 8:13 ` Alex Shi
2013-07-05 14:23 ` Frederic Weisbecker
2013-07-05 14:38 ` Peter Zijlstra
2013-07-05 15:24 ` Thomas Gleixner
2013-07-05 21:22 ` Peter Zijlstra
2013-07-05 21:50 ` Thomas Gleixner
2013-07-05 21:58 ` Borislav Petkov
2013-07-05 22:17 ` Thomas Gleixner
2013-07-06 8:37 ` Borislav Petkov
2013-07-06 10:50 ` Peter Zijlstra
2013-07-04 11:00 ` Thomas Gleixner
2013-07-04 18:11 ` Davidlohr Bueso
2013-07-04 20:27 ` Thomas Gleixner
2013-07-05 1:12 ` Alex Shi [this message]
2013-07-05 5:58 ` Thomas Gleixner
2013-07-05 6:28 ` Alex Shi
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=51D61D97.8060904@intel.com \
--to=alex.shi@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi.kleen@intel.com \
--cc=davidlohr.bueso@hp.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
/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