From: Tony Lindgren <tony@atomide.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dynamic tick for x86 version 050602-1
Date: Wed, 1 Jun 2005 19:09:30 -0700 [thread overview]
Message-ID: <20050602020930.GN21597@atomide.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506011953090.22613@montezuma.fsmlabs.com>
* Zwane Mwaikambo <zwane@arm.linux.org.uk> [050601 18:51]:
> Hi Tony,
>
> On Wed, 1 Jun 2005, Tony Lindgren wrote:
>
> > Here's an updated version of the dynamic tick patch.
> >
> > It's mostly clean-up and it's now using the standard
> > monotonic_clock() functions as suggested by John Stultz.
> >
> > Please let me know of any issues with the patch. I'll continue to do
> > more clean-up on it, but I think the basic functionality is done.
> >
> > Thomas, where do you have the latest version of your ACPI idle
> > patch? I'd like to add that to the dyn-tick page as well.
> >
> > Older patches and some related links are at:
> >
> > http://muru.com/linux/dyntick/
>
> Are there any 'known issues' wrt various timer sources with this version?
AFAIK, these are the remaining issues:
Supported timers are ACPI PM timer and TSC timer. No support for
CONFIG_HPET yet. Anybody feel like adding the HPET support? I don't
have any machines with HPET.
Lost tick code is currently disabled with #ifndef CONFIG_NO_IDLE_HZ
in timer_pm.c and timer_tsc.c. This should be done based on some
variable instead.
Kconfig option DYN_TICK_USE_APIC should be converted to a command
line option, as it only seems to work on P3 and not on P4.
So actually let's say the basic functionality is still missing
some parts :) But these should be pretty easy to fix.
Tony
next prev parent reply other threads:[~2005-06-02 2:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 1:36 [PATCH] Dynamic tick for x86 version 050602-1 Tony Lindgren
2005-06-02 1:54 ` Zwane Mwaikambo
2005-06-02 2:09 ` Tony Lindgren [this message]
2005-06-02 8:30 ` Christian Hesse
2005-06-02 17:42 ` [PATCH] Dynamic tick for x86 version 050602-2 Tony Lindgren
2005-06-02 20:03 ` Christian Hesse
2005-06-02 20:32 ` Tony Lindgren
2005-06-03 6:08 ` Christian Hesse
2005-06-03 17:39 ` Tony Lindgren
2005-06-04 12:51 ` Christian Hesse
2005-06-10 4:03 ` Tony Lindgren
2005-06-05 4:06 ` Bernard Blackham
2005-06-10 4:05 ` Tony Lindgren
2005-06-03 22:37 ` Pavel Machek
2005-06-03 22:47 ` Pavel Machek
2005-06-10 4:17 ` Tony Lindgren
2005-06-10 9:15 ` Pavel Machek
2005-06-10 15:17 ` Tony Lindgren
2005-06-10 22:15 ` [PATCH] Dynamic tick for x86 version 050610-1 Tony Lindgren
2005-06-18 3:34 ` hugang
2005-06-18 6:30 ` Benjamin Herrenschmidt
2005-06-21 1:28 ` Tony Lindgren
2005-06-21 1:49 ` Benjamin Herrenschmidt
2005-06-21 2:21 ` Tony Lindgren
2005-07-19 6:51 ` hugang
2005-07-19 13:51 ` Benjamin Herrenschmidt
2005-07-25 10:11 ` Tony Lindgren
2005-06-11 17:59 ` [PATCH] Dynamic tick for x86 version 050602-2 Kyle Moffett
2005-06-07 20:36 ` [PATCH] Dynamic tick for x86 version 050602-1 Jonathan Corbet
2005-06-10 4:18 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2005-06-08 22:14 Pallipadi, Venkatesh
2005-06-09 1:40 ` Tony Lindgren
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=20050602020930.GN21597@atomide.com \
--to=tony@atomide.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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