From: Len Brown <lenb@kernel.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: johnstul@us.ibm.com, ak@suse.de, linux-kernel@vger.kernel.org,
tglx@linutronix.de
Subject: Re: Fw: [BUG 2.6.21-rc7] acpi_pm clocksource loses time on x86-64
Date: Tue, 8 May 2007 15:14:36 -0400 [thread overview]
Message-ID: <200705081514.36958.lenb@kernel.org> (raw)
In-Reply-To: <200705040742.l447gJPR027148@harpo.it.uu.se>
On Friday 04 May 2007 03:42, Mikael Pettersson wrote:
> On Thu, 03 May 2007 19:38:50 -0700, john stultz wrote:
> > > So that slow acpi_pm on x86_64 seems to be connected w/ the idle loop.
> > > I'm guessing the chipset halts the ACPI PM in lower C states. Do you
> > > have any guesses as to what might differ between x86_64 and i386 ACPI
> > > idle loops? Or might this be something different in what the BIOS
> > > exports in x86_64 mode or i386 mode?
> >
> > Mikael,
> > Just trying to dig a bit more through the acpi_processor_idle code.
> > Could you run "cat /proc/acpi/processor/CPU1/power" and reply w/ the
> > output?
>
> Here's that file with the x86-64 kernel:
>
> active state: C2
> max_cstate: C8
> bus master activity: 00000000
> maximum allowed latency: 20000 usec
> states:
> C1: type[C1] promotion[C2] demotion[--] latency[000] usage[00107840] duration[00000000000000000000]
> *C2: type[C2] promotion[--] demotion[C1] latency[010] usage[-1987043693] duration[00000000003044809185]
it may be that the problem is C2, not C1 on this box and thus "idle=poll" may be
overkill to workaround it.
You can disable C2 with "processor.max_cstate=1"
still a mystery, though, why this is different on i386 vs x86_64.
what is in this file when booted in i386 mode?
-Len
next prev parent reply other threads:[~2007-05-08 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 7:42 Fw: [BUG 2.6.21-rc7] acpi_pm clocksource loses time on x86-64 Mikael Pettersson
2007-05-08 19:14 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-13 21:30 Mikael Pettersson
2007-05-09 9:11 Mikael Pettersson
2007-05-10 18:52 ` john stultz
[not found] <200704291524.l3TFOL9j013216@harpo.it.uu.se>
2007-05-02 18:10 ` john stultz
2007-05-04 2:38 ` john stultz
[not found] <20070417100942.c990604b.akpm@linux-foundation.org>
2007-04-17 20:12 ` john stultz
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=200705081514.36958.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=ak@suse.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.