From: Thomas Gleixner <tglx@linutronix.de>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: aim7 47% regression with 2.6.27-rc8
Date: Mon, 6 Oct 2008 08:59:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0810060858350.3398@apollo> (raw)
In-Reply-To: <1223269135.1685.11.camel@ymzhang>
On Mon, 6 Oct 2008, Zhang, Yanmin wrote:
> Comparing with 2.6.27-rc8, aim7 result has about 47% regression with 2.6.27-rc8 on
> my 16-core tigerton and 8 core+HyperThreading x86_64 machine.
>
> I bisected it down to patch:
>
> 302745699c1b675b5d2a1af87271de10e4d96b6a is first bad commit
> commit 302745699c1b675b5d2a1af87271de10e4d96b6a
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Mon Sep 22 19:02:25 2008 +0200
>
> clockevents: check broadcast device not tick device
>
> Impact: Possible hang on CPU online observed on AMD C1E machines.
>
> The broadcast setup code looks at the mode of the tick device to
> determine whether it needs to be shut down or setup. This is wrong
> when the broadcast mode is set to one shot already. This can happen
> when a CPU is brought online as it goes through the periodic setup
> first.
>
> The problem went unnoticed as sane systems do not call into that code
> before the switch to one shot for the clock event device happens.
> The AMD C1E idle routine switches over immediately and thereby shuts
> down the just setup device before the first interrupt happens.
>
>
> After I reverted the patch against 2.6.27-rc8, the regression disappears.
> It's interesting that the regression doesn't exist on 8-core stoakley.
There is a fixup patch for this one after rc8. 07454bfff151d2465ada809bbaddf3548cc1097c
Can you check with this one applied please ?
Thanks,
tglx
prev parent reply other threads:[~2008-10-06 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 4:58 Zhang, Yanmin
[not found] ` <1223271482.7794.1.camel@marge.simson.net>
2008-10-06 5:52 ` Zhang, Yanmin
2008-10-06 6:59 ` Thomas Gleixner [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=alpine.LFD.2.00.0810060858350.3398@apollo \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin_zhang@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
all inboxes | Powered by JetHome®