From: Frederic Weisbecker <fweisbec@gmail.com>
To: Mike Galbraith <bitbucket@online.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: dynticks: CONFIG_VIRT_CPU_ACCOUNTING + CONFIG_CONTEXT_TRACKING breaks accounting on core2 CPUs only
Date: Tue, 14 May 2013 02:57:46 +0200 [thread overview]
Message-ID: <20130514005744.GA12749@somewhere> (raw)
In-Reply-To: <1368346669.5998.13.camel@marge.simpson.net>
On Sun, May 12, 2013 at 10:17:49AM +0200, Mike Galbraith wrote:
> Greetings,
>
> Turning on new NO_HZ feature on my Q6600 box in master, I see that tasks
> accrue zero utime/stime. However, the same exact kernel on E5620 box
> works fine, so it would appear there's a CPU dependency somewhere.
Ah indeed, I just managed to reproduce the same issue.
>
> Is core2 expected to go dysfunctional with context tracking enabled?
> CONFIG_VIRT_CPU_ACCOUNTING alone works fine in 3.9-stable, turn on
> CONFIG_CONTEXT_TRACKING_FORCE, and CPU accounting stops working on core2
> boxen only, same exact kernel continues to work just fine on E5620
> (Westmere) box.
There was no known issue with core2. The box where I'm seeing the it
is a Phenom quad core that had NR_CPUS=2. May be the issue is more
likely to happen with this low number. I don't know.
I'm investigating further.
Thanks.
next prev parent reply other threads:[~2013-05-14 0:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 8:17 dynticks: CONFIG_VIRT_CPU_ACCOUNTING + CONFIG_CONTEXT_TRACKING breaks accounting on core2 CPUs only Mike Galbraith
2013-05-14 0:57 ` Frederic Weisbecker [this message]
2013-05-14 7:37 ` Mike Galbraith
2013-05-14 14:07 ` Mike Galbraith
2013-05-15 0:26 ` Frederic Weisbecker
2013-05-15 4:09 ` Mike Galbraith
2013-05-15 16:05 ` Frederic Weisbecker
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=20130514005744.GA12749@somewhere \
--to=fweisbec@gmail.com \
--cc=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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