From: Alex Shi <alex.shi@intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, john stultz <johnstul@us.ibm.com>,
venki@google.com, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: kernel panic on NHM EX machine
Date: Thu, 12 Apr 2012 12:16:31 +0800 [thread overview]
Message-ID: <4F86571F.7090005@intel.com> (raw)
In-Reply-To: <20120412024651.GA7250@localhost>
On 04/12/2012 10:46 AM, Fengguang Wu wrote:
> Hi all,
>
> This commit makes a difference. Found by auto bisection and confirmed
> by reverting it on top of v3.4-rc2. Attached is my kconfig.
>
> commit 77b0d60c5adf39c74039e2142a1d3cd1e4d53799
> Author: Suresh Siddha <suresh.b.siddha@intel.com>
> Date: Fri Nov 4 17:18:21 2011 -0700
>
> clockevents: Leave the broadcast device in shutdown mode when not needed
>
> Platforms with Always Running APIC Timer doesn't use the broadcast timer
> but the kernel is leaving the broadcast timer (HPET in this case)
> in oneshot mode.
>
> On these platforms, before the switch to oneshot mode, broadcast device is
> actually in shutdown mode. Code checks for empty tick_broadcast_mask and
> avoids going into the periodic mode.
>
> During switch to oneshot mode, add the same tick_broadcast_mask checks in the
> tick_broadcast_switch_to_oneshot() and avoid the broadcast device going into
> the oneshot mode.
>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
> Cc: john stultz <johnstul@us.ibm.com>
> Cc: venki@google.com
> Link: http://lkml.kernel.org/r/1320452301.15071.16.camel@sbsiddha-desk.sc.intel.com
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
It made loopback netperf performance regression on NHM-EP, I thought it
is due to few local timers missing on EP, but didn't know it is totally
out of work on EX.
next prev parent reply other threads:[~2012-04-12 4:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 11:37 kernel panic on NHM EX machine Alex Shi
2012-04-09 22:31 ` Paul E. McKenney
2012-04-10 1:04 ` Alex Shi
2012-04-10 14:35 ` Paul E. McKenney
2012-04-12 2:46 ` Fengguang Wu
2012-04-12 4:16 ` Alex Shi [this message]
2012-04-12 4:29 ` Suresh Siddha
2012-04-12 6:25 ` Fengguang Wu
2012-04-12 4:58 ` Paul E. McKenney
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=4F86571F.7090005@intel.com \
--to=alex.shi@intel.com \
--cc=fengguang.wu@intel.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venki@google.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