From: Thomas Gleixner <tglx@linutronix.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
mingo@redhat.com, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.19-rc4-mm1: noidlehz problems
Date: Wed, 01 Nov 2006 21:55:01 +0100 [thread overview]
Message-ID: <1162414502.15900.261.camel@localhost.localdomain> (raw)
In-Reply-To: <20061101152201.GA13634@srcf.ucam.org>
On Wed, 2006-11-01 at 15:22 +0000, Matthew Garrett wrote:
> On Wed, Nov 01, 2006 at 02:02:57PM +0100, Arjan van de Ven wrote:
>
> > In some (hardware) C-states, the local apic timer stops (as does the
> > TSC), while in others it keeps running. If you change from AC to
> > battery, the bios can change the meaning of a software C-state from one
> > where local apic timer keeps going to one where it stops. This obviously
> > upsets the hrtimers/tickless code since that uses local apic timer for
> > event generation....
>
> Is there any hope of working around this? I'd have expected that the
> most useful case for the tickless code was also the case where we want
> to be using C3/C4...
Can you try the following patches please ?
http://tglx.de/projects/hrtimers/2.6.19-rc4-mm1/patch-2.6.19-rc4-mm1-hrt-dyntick1.patch
This addresses the C34/C4 issue
tglx
prev parent reply other threads:[~2006-11-01 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 12:23 2.6.19-rc4-mm1: noidlehz problems Pavel Machek
2006-11-01 12:55 ` Pavel Machek
2006-11-01 13:02 ` Arjan van de Ven
2006-11-01 13:20 ` Pavel Machek
2006-11-01 15:22 ` Matthew Garrett
2006-11-01 20:55 ` 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=1162414502.15900.261.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
/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