From: Len Brown <len.brown@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Len Brown <lenb@kernel.org>,
Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com
Subject: Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1]
Date: Tue, 14 Nov 2006 01:34:20 -0500 [thread overview]
Message-ID: <200611140134.21054.len.brown@intel.com> (raw)
In-Reply-To: <20061107080733.GB9910@elte.hu>
On Tuesday 07 November 2006 03:07, Ingo Molnar wrote:
> > So given that C3 on every known system that has shipped to date breaks
> > the LAPIC timer (and apparently this applies to C2 on these AMD
> > boxes), dynticks needs a solid story for co-existing with C3.
>
> check out 2.6.19-rc4-mm2: it detects this breakage and works it around
> by using the PIT as a clock-events source. That did the trick on my
> laptop which has this problem too. I agree with you that degrading the
> powersaving mode is not an option.
>
> we've got a question about HPET: it seems all recent hardware has it,
> but the BIOS rarely mentions it, so the Linux driver does not enable
> HPET. Is there any chance to enable HPET (in the chipset?) - this would
> probably be a higher-quality clock-events source than the PIT.
If Windows enumerates and uses the HPET on a box, then Linux
should be able to use the HPET on that box too.
I belive that Venki has looked at some of the HPET enumeration issues,
and maybe he has some suggestions. Is there an example system
on-hand where we know Windows works and Linux does not?
-Len
next prev parent reply other threads:[~2006-11-14 6:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 14:07 CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1] Andreas Mohr
2006-11-01 21:51 ` Thomas Gleixner
2006-11-02 0:18 ` Andreas Mohr
2006-11-02 7:31 ` Thomas Gleixner
2006-11-02 8:14 ` Thomas Gleixner
2006-11-02 17:22 ` Thomas Gleixner
2006-11-02 19:28 ` Andreas Mohr
2006-11-02 20:34 ` Andreas Mohr
2006-11-03 0:06 ` Andreas Mohr
2006-11-06 16:20 ` Thomas Gleixner
2006-11-06 20:58 ` Andreas Mohr
2006-11-07 6:41 ` Len Brown
2006-11-07 8:07 ` Ingo Molnar
2006-11-07 8:25 ` Thomas Gleixner
2006-11-07 9:16 ` Andreas Mohr
2006-11-07 9:28 ` Thomas Gleixner
2006-11-07 9:45 ` Thomas Gleixner
2006-11-07 22:27 ` Andreas Mohr
2006-11-08 19:36 ` Thomas Gleixner
2006-11-14 6:34 ` Len Brown [this message]
2006-11-07 8:18 ` Andreas Mohr
2006-11-07 8:24 ` Ingo Molnar
2006-11-14 6:27 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 17:21 Pallipadi, Venkatesh
2006-11-14 17:30 ` Andreas Mohr
2006-11-14 18:04 ` Andreas Mohr
2006-12-17 15:58 ` Tobias Diedrich
2006-11-14 18:06 Pallipadi, Venkatesh
2006-11-14 20:30 ` Andreas Mohr
2006-11-14 21:00 ` Andreas Mohr
2006-11-14 21:18 ` Andreas Mohr
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=200611140134.21054.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.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