From: Thomas Gleixner <tglx@linutronix.de>
To: Carsten Emde <C.Emde@osadl.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
RT-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 1/1] ARM AT91 Use IRQF_TIMER flag to prevent early boot crash
Date: Tue, 2 Jun 2015 22:27:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1506022220170.20347@nanos> (raw)
In-Reply-To: <20150602133341.666241244@osadl.org>
On Tue, 2 Jun 2015, Carsten Emde wrote:
> When threaded interrupts are configured, they may not be
> requested before the khtread daemon is running. The system
> crashes at an early boot stage, otherwise:
<SNIP>
> Add the IRQF_TIMER flag as recommended by Sebastian Siewior
> -> http://www.spinics.net/lists/linux-rt-users/msg13171.html
This is wrong. The interrupts in question are not timers in the sense
of system timers. They are related to the clock subsystem and have a
totally different purpose, i.e. they are just there to wake up waiters
which wait for the synchronization of a particular clock, pll ...
So the proper flag is IRQF_NO_THREAD. And that's not a RT problem,
that's a mainline problem as well, if 'threadirqs' is set on the
kernel command line.
Now even if you add IRQF_NO_THREAD then still the interrupt service
routine is not RT compatible:
static irqreturn_t clk_main_osc_irq_handler(int irq, void *dev_id)
{
struct clk_main_osc *osc = dev_id;
wake_up(&osc->wait);
^^^ takes sleeping spinlocks
Thanks,
tglx
prev parent reply other threads:[~2015-06-02 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 13:29 [PATCH 1/1] ARM AT91 Use IRQF_TIMER flag to prevent early boot crash Carsten Emde
2015-06-02 20:27 ` Thomas Gleixner [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=alpine.DEB.2.11.1506022220170.20347@nanos \
--to=tglx@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.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