From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Remy Bohmer <linux@bohmer.net>,
RT <linux-rt-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
Date: Wed, 28 Nov 2007 16:13:07 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.58.0711281608490.26365@gandalf.stny.rr.com> (raw)
In-Reply-To: <1196282672.27964.32.camel@imap.mvista.com>
On Wed, 28 Nov 2007, Daniel Walker wrote:
>
> Ignoring the ARM side of things for a sec, handle_simple_irq() will
> mask() the interrupt in the special case that an interrupt is already in
> the processes of being handled.. handle_simple_irq() also unmasks when
> it finishes handling an interrupt (something real time adds for some
> reason) ..
>
> In terms of threading the irq everything is the same except there is no
> unmask() call when the thread finishes ..
>
OK, to be honest, I never fully understood the concept of this
"simple_irq". I figured it was because of the ARM architecture.
Your arguments seem reasonable and you are probably correct. But I didn't
write this code, nor do I understand it, and before I go ahead and change
it, I'll wait to hear input from Thomas. Hopefully, he'll be back soon.
Perhaps my confusion about the simple_irq part is from the bug you are
trying to fix. I've been confused by why it was different ;-)
-- Steve
next prev parent reply other threads:[~2007-11-28 21:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 13:31 [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever Remy Bohmer
2007-11-26 13:45 ` Remy Bohmer
2007-11-27 15:11 ` Steven Rostedt
2007-11-27 15:25 ` Daniel Walker
2007-11-27 15:53 ` Daniel Walker
2007-11-28 14:38 ` Remy Bohmer
2007-11-28 15:36 ` Daniel Walker
2007-11-28 17:25 ` Russell King - ARM Linux
2007-11-28 19:04 ` Steven Rostedt
2007-11-28 20:05 ` Russell King - ARM Linux
2007-11-28 20:16 ` Steven Rostedt
2007-11-28 20:44 ` Daniel Walker
2007-11-28 21:13 ` Steven Rostedt [this message]
2007-11-28 23:03 ` Russell King - ARM Linux
2007-11-28 23:19 ` Daniel Walker
2007-11-29 9:04 ` Russell King - ARM Linux
2007-11-29 10:14 ` Remy Bohmer
2007-11-29 10:25 ` Russell King - ARM Linux
2007-11-29 11:27 ` Remy Bohmer
2007-11-29 13:36 ` Russell King - ARM Linux
2007-11-29 13:57 ` Steven Rostedt
2007-11-29 14:18 ` Remy Bohmer
2007-11-29 14:29 ` Russell King - ARM Linux
2007-11-29 15:33 ` Remy Bohmer
2007-11-29 16:20 ` Remy Bohmer
2007-11-29 16:30 ` Steven Rostedt
2007-11-30 21:44 ` Thomas Gleixner
2007-12-12 19:40 ` [PATCH RT] Revert Softdisable for simple irqs Steven Rostedt
2007-12-12 19:46 ` Russell King
2007-12-12 20:05 ` Remy Bohmer
2007-12-12 20:27 ` Steven Rostedt
2007-12-12 21:38 ` Remy Bohmer
[not found] ` <87bq9fqpoi.fsf@vence.hilman.org>
2007-11-28 14:43 ` [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever Remy Bohmer
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=Pine.LNX.4.58.0711281608490.26365@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=dwalker@mvista.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@bohmer.net \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).