From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, hbausley@deltatau.com
Subject: Re: Critical Interrupt Input
Date: Sun, 18 Aug 2013 08:05:22 +1000 [thread overview]
Message-ID: <1376777122.25016.9.camel@pasglop> (raw)
In-Reply-To: <DA804F98-B7E5-42C1-9D5C-8A8A63681EC0@kernel.crashing.org>
On Fri, 2013-08-16 at 06:04 -0500, Kumar Gala wrote:
> The 44x low level code needs to handle exception stacks properly for
> this to work. Since its possible to have a critical exception occur
> while in a normal exception level, you have to have proper saving of
> additional register state and a stack frame for the critical
> exception, etc. I'm not sure if that was ever done for 44x.
Don't 44x and FSL BookE share the same macros ? I would think 44x does
indeed implement the same crit support as e500...
What does the crash look like ?
Ben.
next prev parent reply other threads:[~2013-08-17 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 4:57 Critical Interrupt Input Henry Bausley
2013-08-16 11:04 ` Kumar Gala
2013-08-17 22:05 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-19 19:00 Henry Bausley
2013-08-19 20:56 ` Benjamin Herrenschmidt
2013-08-19 21:04 ` Denis Kirjanov
2013-08-20 22:48 ` Henry Bausley
2013-08-20 23:08 ` Benjamin Herrenschmidt
2013-08-27 22:11 ` Henry Bausley
2013-08-27 22:14 ` Benjamin Herrenschmidt
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=1376777122.25016.9.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=hbausley@deltatau.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).