From: Matt Porter <mporter@kernel.crashing.org>
To: Felix Domke <tmbinc@elitedvb.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 405 Critical Interrupts
Date: Wed, 26 Nov 2003 13:48:14 -0700 [thread overview]
Message-ID: <20031126134814.A9704@home.com> (raw)
In-Reply-To: <3FC4D4B5.2030901@elitedvb.net>; from tmbinc@elitedvb.net on Wed, Nov 26, 2003 at 05:28:37PM +0100
On Wed, Nov 26, 2003 at 05:28:37PM +0100, Felix Domke wrote:
> I thought about routing the CriticalInterrupt pretty much the same way
> as the HardwareInterrupt, but with disabling MSR_CE. MSR_CE would be
> enabled then even in (normal) interrupts, we probably have to add a
> __crit_cli and __save_and_crit_cli as someone already suggested.
>
> Does CRIT_EXCEPTION work? Is do_IRQ reentrant? Should i use the same
> interrupt processing as a normal hardware interrupt, with the exception
> that only "critical"-flagged interrupts are processed?
>
> Any suggestions?
You could backport the critical exception handling code from 2.6.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-26 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 16:28 405 Critical Interrupts Felix Domke
2003-11-26 20:48 ` Matt Porter [this message]
2003-11-27 2:12 ` Takeharu KATO
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=20031126134814.A9704@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tmbinc@elitedvb.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.