From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Russell King <linux@arm.linux.org.uk>,
Chris Ball <chris@printf.net>,
linux-mmc@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: [patch 0/2] genirq: Add functions to avoid driver hackery
Date: Sat, 15 Feb 2014 00:55:18 -0000 [thread overview]
Message-ID: <20140215002742.507053194@linutronix.de> (raw)
Russell tricked me to look into the homebrewn kthread hackery of
drivers/mmc. I'm still trying to recover from that.
But it spurred an interesting discussion how to improve things and the
outcome was the following series of patches:
1) Provide means to synchronize only hard irq context
2) Provide means to trigger a threaded irq handler from any context
The main rationale is to cleanup the mess in drivers/mmc and other
places but each of the patches has a justification for itself
exemplified by the drivers/mmc use case, which is explained in detail
in the changelogs of the individual patches.
Russell has a working implementation for sdhci which relies on patch
#1 ready and quite some ideas how to make use of #2 to kill the
sdio_irq kthread hackery.
Thanks,
tglx
next reply other threads:[~2014-02-15 0:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 0:55 Thomas Gleixner [this message]
2014-02-15 0:55 ` [patch 1/2] genirq: Provide synchronize_hardirq() Thomas Gleixner
2014-02-15 9:50 ` Peter Zijlstra
2014-02-19 16:27 ` [tip:irq/core] " tip-bot for Thomas Gleixner
2014-02-15 0:55 ` [patch 2/2] genirq: Provide irq_wake_thread() Thomas Gleixner
2014-02-15 9:50 ` Peter Zijlstra
2014-02-19 16:27 ` [tip:irq/core] " tip-bot for 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=20140215002742.507053194@linutronix.de \
--to=tglx@linutronix.de \
--cc=chris@printf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®