From: Tony Lindgren <tony@atomide.com>
To: Thomas Gleixner <tglx@linutronix.de>
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 01:51:00 -0800 [thread overview]
Message-ID: <20060228095100.GA31105@atomide.com> (raw)
In-Reply-To: <1141117500.5237.112.camel@localhost.localdomain>
* Thomas Gleixner <tglx@linutronix.de> [060228 01:03]:
> On Mon, 2006-02-27 at 19:29 -0800, Tony Lindgren wrote:
> > I've changed ARM xtime_lock to read lock, but now there's a slight
> > chance that an interrupt adds a timer after next_timer_interrupt() is
> > called and before timer is reprogrammed. I believe s390 also has this
> > problem.
>
> This needs a more generalized solution later, but I picked up your ARM
> change and simplified the hrtimer related bits.
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.
Regards,
Tony
next prev parent reply other threads:[~2006-02-28 9:51 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 ` + fix-next_timer_interrupt-for-hrtimer.patch added to -mm tree 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 [this message]
2006-02-28 10:06 ` Thomas Gleixner
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=20060228095100.GA31105@atomide.com \
--to=tony@atomide.com \
--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=tglx@linutronix.de \
/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.