From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <ak@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
Arjan van de Ven <arjan@infradead.org>,
Dave Jones <davej@redhat.com>,
David Woodhouse <dwmw2@infradead.org>, Jim Gettys <jg@laptop.org>,
Roman Zippel <zippel@linux-m68k.org>,
akpm@osdl.org
Subject: Re: [patch 00/22] high resolution timers / dynamic ticks - V3
Date: Thu, 05 Oct 2006 23:11:56 +0200 [thread overview]
Message-ID: <1160082716.9060.105.camel@localhost.localdomain> (raw)
In-Reply-To: <p73fye2zdjf.fsf@verdi.suse.de>
On Thu, 2006-10-05 at 22:57 +0200, Andi Kleen wrote:
> > ah, that's still the VAIO, right? Do you get a 'slow' LOC count on
> > /proc/interrupts even on a stock kernel? If yes then that's a
> > fundamentally sick local APIC timer interrupt. Stock kernel should show
> > sickness too, if for example you boot an SMP kernel on it - can you
> > confirm that? (the UP-IOAPIC only relies for profiling on the lapic
> > timer, so there the only sickness you should see on the stock kernel is
> > a non-working readprofile)
>
> When I was hacking on my old noidletick patch I ran into this
> problem on several machines too.
>
> But usually the problem wasn't that it was too slow, but that
> it completely stopped in C2 or deeper. I don't think there
> is a way to work around that except for not using C2 or deeper
> (not an option) or using a different timer source.
>
> If that is true then hitting space lots of time will make it
> go faster.
If that's the case we can even autodetect it and stay with PIT and
ignore lapic all the way.
tglx
next prev parent reply other threads:[~2006-10-05 21:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 17:31 [patch 00/22] high resolution timers / dynamic ticks - V3 Thomas Gleixner
2006-10-04 17:31 ` [patch 01/22] GTOD: exponential update_wall_time Thomas Gleixner
2006-10-04 17:31 ` [patch 02/22] GTOD: persistent clock support, core Thomas Gleixner
2006-10-04 17:31 ` [patch 03/22] GTOD: persistent clock support, i386 Thomas Gleixner
2006-10-04 17:31 ` [patch 04/22] time: uninline jiffies.h Thomas Gleixner
2006-10-04 17:31 ` [patch 05/22] time: fix msecs_to_jiffies() bug Thomas Gleixner
2006-10-04 17:31 ` [patch 06/22] time: fix timeout overflow Thomas Gleixner
2006-10-04 17:31 ` [patch 07/22] cleanup: uninline irq_enter() and move it into a function Thomas Gleixner
2006-10-04 17:31 ` [patch 08/22] dynticks: extend next_timer_interrupt() to use a reference jiffie Thomas Gleixner
2006-10-04 17:31 ` [patch 09/22] hrtimers: namespace and enum cleanup Thomas Gleixner
2006-10-04 17:31 ` [patch 10/22] hrtimers: clean up locking Thomas Gleixner
2006-10-04 17:31 ` [patch 11/22] hrtimers: state tracking Thomas Gleixner
2006-10-04 17:31 ` [patch 12/22] hrtimers: clean up callback tracking Thomas Gleixner
2006-10-04 17:31 ` [patch 13/22] hrtimers: Move and add documentation Thomas Gleixner
2006-10-04 17:31 ` [patch 14/22] clockevents: core Thomas Gleixner
2006-10-04 17:31 ` [patch 15/22] clockevents: drivers for i386 Thomas Gleixner
2006-10-04 17:31 ` [patch 16/22] high-res timers: core Thomas Gleixner
2006-10-04 17:31 ` [patch 17/22] GTOD: Mark TSC unusable for highres timers Thomas Gleixner
2006-10-04 17:31 ` [patch 18/22] dynticks: core Thomas Gleixner
2006-10-04 17:31 ` [patch 19/22] dyntick: add nohz stats to /proc/stat Thomas Gleixner
2006-10-04 17:31 ` [patch 20/22] dynticks: i386 arch code Thomas Gleixner
2006-10-04 17:31 ` [patch 21/22] high-res timers, dynticks: enable i386 support Thomas Gleixner
2006-10-04 17:31 ` [patch 22/22] debugging feature: timer stats Thomas Gleixner
2006-10-05 8:16 ` [patch 00/22] high resolution timers / dynamic ticks - V3 Andrew Morton
2006-10-05 8:11 ` Ingo Molnar
2006-10-05 8:17 ` Ingo Molnar
2006-10-05 20:57 ` Andi Kleen
2006-10-05 21:11 ` Thomas Gleixner [this message]
2006-10-06 7:28 ` Arjan van de Ven
2006-10-16 10:53 ` Andi Kleen
2006-10-05 8:19 ` Andrew Morton
2006-10-05 8:23 ` Ingo Molnar
2006-10-05 8:50 ` Andrew Morton
2006-10-05 9:48 ` 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=1160082716.9060.105.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jg@laptop.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=valdis.kletnieks@vt.edu \
--cc=zippel@linux-m68k.org \
/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.