From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Len Brown <lenb@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, "Van De Ven,
Arjan" <arjan.van.de.ven@intel.com>
Subject: Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1]
Date: Tue, 14 Nov 2006 19:04:21 +0100 [thread overview]
Message-ID: <20061114180421.GA1910@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <20061114173054.GA27092@rhlx01.hs-esslingen.de>
On Tue, Nov 14, 2006 at 06:30:54PM +0100, Andreas Mohr wrote:
> Hmm, hopefully it's easy to research where to enable HPET
> (if there is one at all!) on an el-cheapo VIA chipset...
http://forum.insanelymac.com/index.php?showtopic=31399&pid=219051&st=0&#entry219051
"The VIA VT8237 chipset also support HPET."
And this is confirmed by:
http://www.nabble.com/-PATCH--HPET:-do-not-use-64-bit-reads-t2500136.html
"However, there is no guarantee that the timer actually has 64 bits, the
specification only recommends it. My x86-64 system has a 32-bit timer
(AMD64 with a VT8237 southbridge). "
Hmm, and I'm afraid I have a VT8235 only which possibly doesn't have HPET :-P
A relatively detailed (covers Windows XP timer details) HPET etc.
x86 timers discussion is at
"[Comp-arch] x86 High Precision Event Timers support"
https://www.gelato.unsw.edu.au/archives/comp-arch/2006-June/001320.html
Andreas Mohr
next prev parent reply other threads:[~2006-11-14 18:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 17:21 Pallipadi, Venkatesh
2006-11-14 17:30 ` Andreas Mohr
2006-11-14 18:04 ` Andreas Mohr [this message]
2006-12-17 15:58 ` Tobias Diedrich
-- strict thread matches above, loose matches on Subject: below --
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
2006-11-01 14:07 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
2006-11-07 8:18 ` Andreas Mohr
2006-11-07 8:24 ` Ingo Molnar
2006-11-14 6:27 ` Len Brown
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=20061114180421.GA1910@rhlx01.hs-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=arjan.van.de.ven@intel.com \
--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
all inboxes | Powered by JetHome®