From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: nohz and strange sleep latencies
Date: Sun, 25 Nov 2007 00:35:26 +0100 [thread overview]
Message-ID: <200711250035.27400.rjw@sisk.pl> (raw)
In-Reply-To: <200711250029.55461.rjw@sisk.pl>
On Sunday, 25 of November 2007, Rafael J. Wysocki wrote:
> On Saturday, 24 of November 2007, Pavel Machek wrote:
> > Hi!
> >
> > > > > but perhaps somehow we miss this fact and fail to turn off the lapic
> > > > > clockevents drivers?
> > > >
> > > > Ok, I guess I'm lost. If I offline second CPU, I immediately get
> > > > 1000Hz timer tick... is that expected?
> > >
> > > Hmm. No. I have no idea why this is happening.
> > >
> > > 34196 total events, 55.083 events/sec
> > > echo 0 >/sys/devices/system/cpu/cpu1/online
> > > 36073 total events, 54.679 events/sec
> >
> > Digging into process_32|64.c...
> >
> > 64:
> > while (1) {
> > while (!need_resched()) {
> > void (*idle)(void);
> >
> > if (__get_cpu_var(cpu_idle_state))
> > __get_cpu_var(cpu_idle_state) = 0;
> >
> > tick_nohz_stop_sched_tick();
> >
> > 32:
> > while (1) {
> > tick_nohz_stop_sched_tick();
> > while (!need_resched()) {
> > void (*idle)(void);
> >
> > if (__get_cpu_var(cpu_idle_state))
> > __get_cpu_var(cpu_idle_state) = 0;
> >
> > ...eek? Which one is wrong?
>
> Hm, it looks like you should have quoted more lines ...
>
> In the second case (32), the tick_nohz_stop_sched_tick() seems to be
> redundant, so I bet it's this one.
OTOH, the ARM's process.c is more similar to process_32.c ...
next prev parent reply other threads:[~2007-11-24 23:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 20:31 nohz and strange sleep latencies Pavel Machek
2007-11-19 20:55 ` Ingo Molnar
2007-11-19 21:11 ` Pavel Machek
2007-11-20 8:57 ` Ingo Molnar
2007-11-20 9:05 ` Ingo Molnar
2007-11-20 10:54 ` Pavel Machek
2007-11-20 20:54 ` Ingo Molnar
2007-11-20 22:48 ` Thomas Gleixner
2007-11-20 22:52 ` Ingo Molnar
2007-11-22 10:09 ` Pavel Machek
2007-11-22 18:51 ` Pavel Machek
2007-11-22 18:52 ` Pavel Machek
2007-11-22 20:29 ` Thomas Gleixner
2007-11-23 12:22 ` Pavel Machek
2007-11-24 22:29 ` Pavel Machek
2007-11-24 22:40 ` Pavel Machek
2007-11-24 23:29 ` Rafael J. Wysocki
2007-11-24 23:35 ` Rafael J. Wysocki [this message]
2007-11-25 21:51 ` Thomas Gleixner
2007-11-25 20:25 ` [patch] " Pavel Machek
2007-11-25 21:42 ` Thomas Gleixner
2007-11-26 11:54 ` Pavel Machek
2007-11-20 9:44 ` Thomas Gleixner
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=200711250035.27400.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
/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