From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] irq_work changes for 3.9
Date: Thu, 24 Jan 2013 12:51:23 +0100 [thread overview]
Message-ID: <20130124115123.GC32574@gmail.com> (raw)
In-Reply-To: <1358345841-29136-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Hi Ingo,
>
> The printk changes for full dynticks support are still pending while
> we don't know Linus's opinion about these. Meanwhile here is the
> part of it that I think is uncontroversial. This way we can make
> the next submission attempt to Linus a bit more simple.
>
> These three patches are general fixes for irq work. The two first
> patches fix tight races on global irq work claiming that prevent the irq work
> subsystem from dropping a work enqueuing attempt because it thinks it's
> already pending while it may be already executing or executed.
>
> The last patch just extends irq work support everywhere. It's also a
> kconfig cleanup.
>
> The branch can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> core/irq_work
>
> Head is: 6147a9d8070e1c9d16d57eb53a14942b95b28dc4
>
> Thanks.
>
> ---
> Frederic Weisbecker (3):
> irq_work: Fix racy IRQ_WORK_BUSY flag setting
> irq_work: Fix racy check on work pending flag
> irq_work: Remove CONFIG_HAVE_IRQ_WORK
>
> arch/alpha/Kconfig | 1 -
> arch/arm/Kconfig | 1 -
> arch/arm64/Kconfig | 1 -
> arch/blackfin/Kconfig | 1 -
> arch/frv/Kconfig | 1 -
> arch/hexagon/Kconfig | 1 -
> arch/mips/Kconfig | 1 -
> arch/parisc/Kconfig | 1 -
> arch/powerpc/Kconfig | 1 -
> arch/s390/Kconfig | 1 -
> arch/sh/Kconfig | 1 -
> arch/sparc/Kconfig | 1 -
> arch/x86/Kconfig | 1 -
> drivers/staging/iio/trigger/Kconfig | 1 -
> init/Kconfig | 4 ----
> kernel/irq_work.c | 21 +++++++++++++++------
> 16 files changed, 15 insertions(+), 24 deletions(-)
Pulled into tip:irq/core, thanks Frederic!
Ingo
prev parent reply other threads:[~2013-01-24 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 14:17 [GIT PULL] irq_work changes for 3.9 Frederic Weisbecker
2013-01-16 22:04 ` Andreas Mohr
2013-01-16 22:12 ` Frederic Weisbecker
2013-01-16 22:48 ` Andreas Mohr
2013-01-24 11:51 ` Ingo Molnar [this message]
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=20130124115123.GC32574@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox