From: Linus Walleij <linus.walleij@linaro.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Mainlining PREEMPT_RT
Date: Wed, 14 Oct 2015 09:35:08 +0200 [thread overview]
Message-ID: <CACRpkdb83Q+y9Fd+SmyNi_Fo5wGzmKDKGYFJvpMWSHjC0f=4Ew@mail.gmail.com> (raw)
In-Reply-To: <20151013124230.1a082d28@gandalf.local.home>
On Tue, Oct 13, 2015 at 6:42 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> The various topics would include:
>
> CPU hotplug
> preempt_disable and local_irq_disable annotations
> new timer_wheel implementation
> simple waitqueues
> trylock boosting
- Decide on a case-per-case basis whether to make all irqchips threaded.
We recently ran into this in the GPIO subsystem as Grygorii Strashko
is working on RT on the ARM OMAP. So I drafted a checklist:
http://marc.info/?l=linux-gpio&m=144382150627266&w=2
Feedback welcome. I don't know if I even got the details right in that
checklist. There are a few irqchips around:
$ git grep 'struct irq_chip ' arch/ drivers/ | wc -l
721
If this isn't done I guess that for example a sudden IRQ on a GPIO
pin can delay a deadline. Not good.
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-10-14 7:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 16:42 Steven Rostedt
2015-10-13 17:33 ` Josh Triplett
2015-10-13 22:40 ` Rafael J. Wysocki
2015-10-13 22:19 ` Luis R. Rodriguez
2015-10-13 22:39 ` Steven Rostedt
2015-10-13 22:48 ` Luis R. Rodriguez
2015-10-13 23:04 ` Rafael J. Wysocki
2015-10-13 22:41 ` Luis R. Rodriguez
2015-10-14 7:35 ` Linus Walleij [this message]
2015-10-14 11:45 ` Christoph Lameter
2015-10-14 13:20 ` Steven Rostedt
2015-10-14 14:49 ` Christoph Lameter
2015-10-14 15:22 ` Steven Rostedt
2015-10-14 18:12 ` Christoph Lameter
2015-10-14 18:32 ` Steven Rostedt
2015-10-14 18:56 ` Christoph Lameter
2015-10-14 19:17 ` James Bottomley
2015-10-14 19:30 ` Tim Bird
2015-10-15 2:20 ` Steven Rostedt
2015-10-15 9:05 ` Thomas Gleixner
2015-10-14 20:24 ` Thomas Gleixner
2015-10-15 14:22 ` Christoph Lameter
2015-10-15 15:13 ` Steven Rostedt
2015-10-15 17:21 ` Jan Kara
2015-10-15 18:09 ` Steven Rostedt
2015-10-15 20:21 ` Thomas Gleixner
2015-10-15 20:37 ` Thomas Gleixner
2016-08-05 22:32 ` Darren Hart
2016-08-05 22:40 ` Darren Hart
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='CACRpkdb83Q+y9Fd+SmyNi_Fo5wGzmKDKGYFJvpMWSHjC0f=4Ew@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=rostedt@goodmis.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