From: Thomas Gleixner <tglx@linutronix.de>
To: Tony Lindgren <tony@atomide.com>
Cc: akpm@osdl.org, heiko.carstens@de.ibm.com, johnstul@us.ibm.com,
rmk@arm.linux.org.uk, schwidefsky@de.ibm.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: + fix-next_timer_interrupt-for-hrtimer.patch added to -mm tree
Date: Tue, 28 Feb 2006 11:06:31 +0100 [thread overview]
Message-ID: <1141121191.5237.130.camel@localhost.localdomain> (raw)
In-Reply-To: <20060228095100.GA31105@atomide.com>
Tony,
On Tue, 2006-02-28 at 01:51 -0800, Tony Lindgren wrote:
> Cool, after a quick test seems to work OK here. Any ideas how to fix the
> locking problem above?
>
> Maybe one option would be to just reprogram the hardware timer when a
> new hrtimer is added. That would then allow subjiffie timers too.
You might have a look into the high resolution timer patches on top of
hrtimers at http://www.tglx.de/projects/hrtimers
The clockevents abstraction layer is a quick attempt to generalize the
problem around event generation. I'm stuck in some other work right now,
but I'm going to rework this layer soon. IMO John Stultz GTOD patches
and the generalization of clock events will be a sane base for high
resolution timers and dynamic ticks.
tglx
next prev parent reply other threads:[~2006-02-28 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602250219.k1P2JLqY018864@shell0.pdx.osdl.net>
2006-02-25 16:17 ` Thomas Gleixner
2006-02-25 18:57 ` Tony Lindgren
2006-02-28 3:29 ` Tony Lindgren
2006-02-28 9:05 ` Thomas Gleixner
2006-02-28 9:51 ` Tony Lindgren
2006-02-28 10:06 ` Thomas Gleixner [this message]
2006-02-28 19:34 ` Tony Lindgren
2006-02-28 8:36 ` 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=1141121191.5237.130.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=heiko.carstens@de.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=schwidefsky@de.ibm.com \
--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
Powered by JetHome