From: Christian Hesse <mail@earthworm.de>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dynamic tick for x86 version 050602-2
Date: Thu, 2 Jun 2005 22:03:18 +0200 [thread overview]
Message-ID: <200506022203.27734.mail@earthworm.de> (raw)
In-Reply-To: <20050602174219.GC21363@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]
On Thursday 02 June 2005 19:42, Tony Lindgren wrote:
> * Christian Hesse <mail@earthworm.de> [050602 01:31]:
> > On Thursday 02 June 2005 03:36, Tony Lindgren wrote:
> > > Hi all,
> > >
> > > 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.
> >
> > I would like to test it, but have some trouble. The patch applies cleanly
> > and everything compiles fine, but linking fails:
> >
> > [ linker errors ]
>
> Should be fixed now, the header was defining it as a function un UP
> system with no local apic. Can you try the following version?
This one compiles and links without problems.
The reason I want to use this patch is that I hear a high pitched noise [1]
when running with 1000Hz and the processor is idle. With this patch I could
use 1000Hz without any noise.
But I found some problems on my system:
- time does not run the correct speed, it was some minutes in future after I
had compiled a new kernel
- pressing a key on the keyboard sometimes results in two or more characters,
not only one
- mouse misses some events, e.g. clicks are not recognized (synaptics
touchpad)
- using software suspend 2.1.8.10 I can suspend the system, but it hangs while
resuming
Anyway, thanks for your great work! Let me know if you have new versions to
test.
[1] http://bugme.osdl.org/show_bug.cgi?id=2478
--
Christian
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2005-06-02 20:17 UTC|newest]
Thread overview: 30+ 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
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 [this message]
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
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=200506022203.27734.mail@earthworm.de \
--to=mail@earthworm.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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