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 <mi...@kernel.org>
Date: Wed May 29 11:21:59 2013 +0200
Merge branch 'timers/urgent'
...
commit 7d194f78bde64ec813c1ed8291181bdd61515e78
Merge: 0298bf7 1eaff67
Author: Ingo Molnar <mi...@kernel.org>
Date: Tue May 28 09:53:41 2013 +0200
Merge branch 'timers/core'
commit 0298bf70644d7334bec16ae47f3aa58f4f883b59
Merge: cc662fa 2938d27
Author: Ingo Molnar <mi...@kernel.org>
Date: Tue May 28 09:49:51 2013 +0200
Merge branch 'timers/urgent'
--
Thanks
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
