From: Daniel Walker <dwalker@mvista.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Sven Dietrich <sdietrich@mvista.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: Preempt Real-time for ARM
Date: 09 Feb 2005 09:41:10 -0800 [thread overview]
Message-ID: <1107970869.10177.12.camel@dhcp153.mvista.com> (raw)
In-Reply-To: <20050209125044.A6312@flint.arm.linux.org.uk>
On Wed, 2005-02-09 at 04:50, Russell King wrote:
> What you'll find is that the ARM interrupt structure is designed to
> efficiently meet the requirements of our wide range of hardware interrupt
> controllers, with chained interrupt controllers, with as low latency as
> possible.
>
> In essence, I'm opposed to completely rewriting the ARM interrupt
> handling at this stage.
Everyone wants this as the final solution, but all I want right now is
to have a clean patch for ARM RT .. It would be nice if ARM had the
generics, but It's not _my_ goal.
All I want to do is integrate the common IRQ threading code. To do that
I need things , from Russell, like per descriptor locks .. And I need
things , from Ingo, like pulling out the IRQ threading code..
Daniel
next prev parent reply other threads:[~2005-02-09 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 18:36 Daniel Walker
2005-02-09 11:28 ` Thomas Gleixner
2005-02-09 11:31 ` Ingo Molnar
2005-02-09 11:53 ` Thomas Gleixner
2005-02-09 12:50 ` Russell King
2005-02-09 14:07 ` Thomas Gleixner
2005-02-09 17:41 ` Daniel Walker [this message]
2005-02-09 19:44 ` Russell King
2005-02-10 8:21 ` Eugeny S. Mints
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=1107970869.10177.12.camel@dhcp153.mvista.com \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=sdietrich@mvista.com \
--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
all inboxes | Powered by JetHome®