From: Tejun Heo <tj@kernel.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
tglx@linutronix.de
Subject: Re: [tip:timers/core] timer: Implement TIMER_IRQSAFE
Date: Tue, 21 Aug 2012 12:26:51 -0700 [thread overview]
Message-ID: <20120821192651.GA7701@google.com> (raw)
In-Reply-To: <tip-c5f66e99b7cb091e3d51ae8e8156892e8feb7fa3@git.kernel.org>
On Tue, Aug 21, 2012 at 09:43:07AM -0700, tip-bot for Tejun Heo wrote:
> Commit-ID: c5f66e99b7cb091e3d51ae8e8156892e8feb7fa3
> Gitweb: http://git.kernel.org/tip/c5f66e99b7cb091e3d51ae8e8156892e8feb7fa3
> Author: Tejun Heo <tj@kernel.org>
> AuthorDate: Wed, 8 Aug 2012 11:10:28 -0700
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Tue, 21 Aug 2012 16:28:31 +0200
>
> timer: Implement TIMER_IRQSAFE
>
> Timer internals are protected with irq-safe locks but timer execution
> isn't, so a timer being dequeued for execution and its execution
> aren't atomic against IRQs. This makes it impossible to wait for its
> completion from IRQ handlers and difficult to shoot down a timer from
> IRQ handlers.
>
> This issue caused some issues for delayed_work interface. Because
> there's no way to reliably shoot down delayed_work->timer from IRQ
> handlers, __cancel_delayed_work() can't share the logic to steal the
> target delayed_work with cancel_delayed_work_sync(), and can only
> steal delayed_works which are on queued on timer. Similarly, the
> pending mod_delayed_work() can't be used from IRQ handlers.
>
> This patch adds a new timer flag TIMER_IRQSAFE, which makes the timer
> to be executed without enabling IRQ after dequeueing such that its
> dequeueing and execution are atomic against IRQ handlers.
>
> This makes it safe to wait for the timer's completion from IRQ
> handlers, for example, using del_timer_sync(). It can never be
> executing on the local CPU and if executing on other CPUs it won't be
> interrupted until done.
>
> This will enable simplifying delayed_work cancel/mod interface.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: torvalds@linux-foundation.org
> Cc: peterz@infradead.org
> Link: http://lkml.kernel.org/r/1344449428-24962-5-git-send-email-tj@kernel.org
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Will pull into wq/for-3.7 and put delay_work changes on top. If
there's any objection, please scream.
Thanks a lot.
--
tejun
next prev parent reply other threads:[~2012-08-21 19:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 18:10 Tejun Heo
2012-08-08 18:10 ` [PATCH 1/4] timer: generalize timer->base flags handling Tejun Heo
2012-08-21 16:40 ` [tip:timers/core] timer: Generalize " tip-bot for Tejun Heo
2012-08-08 18:10 ` [PATCH 2/4] timer: relocate declarations of init_timer_on_stack_key() Tejun Heo
2012-08-21 16:41 ` [tip:timers/core] timer: Relocate " tip-bot for Tejun Heo
2012-08-08 18:10 ` [PATCH 3/4] timer: clean up timer initializers Tejun Heo
2012-08-21 16:42 ` [tip:timers/core] timer: Clean " tip-bot for Tejun Heo
2012-08-08 18:10 ` [PATCH 4/4] timer: implement TIMER_IRQSAFE Tejun Heo
2012-08-21 16:43 ` [tip:timers/core] timer: Implement TIMER_IRQSAFE tip-bot for Tejun Heo
2012-08-21 19:26 ` Tejun Heo [this message]
2012-08-08 18:13 ` $SUBJ should have been "[PATCHSET] timer: clean up initializers and implement irqsafe timers" Tejun Heo
2012-08-13 23:35 ` [PATCHSET] timer: clean up initializers and implement irqsafe timers Tejun Heo
2012-08-14 8:32 ` Thomas Gleixner
2012-08-14 19:16 ` Thomas Gleixner
2012-08-14 19:22 ` Tejun Heo
2012-08-14 21:03 ` Thomas Gleixner
2012-08-14 21:56 ` Tejun Heo
2012-08-14 22:45 ` Thomas Gleixner
2012-08-14 23:01 ` Tejun Heo
2012-08-14 23:33 ` Thomas Gleixner
2012-08-15 0:18 ` Tejun Heo
2012-08-15 10:58 ` Peter Zijlstra
2012-08-16 19:36 ` Tejun Heo
2012-08-14 18:55 ` Thomas Gleixner
2012-08-14 19:15 ` Tejun Heo
2012-08-14 20:43 ` Thomas Gleixner
2012-08-14 21:40 ` Tejun Heo
2012-08-14 23:12 ` Thomas Gleixner
2012-08-14 23:27 ` Tejun Heo
2012-08-14 23:46 ` Thomas Gleixner
2012-08-14 23:52 ` Tejun Heo
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=20120821192651.GA7701@google.com \
--to=tj@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--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.