From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] [POWERPC] convert transfer_to_handler into a macro
Date: Wed, 30 Apr 2008 16:32:08 +1000 [thread overview]
Message-ID: <1209537128.18023.225.camel@pasglop> (raw)
In-Reply-To: <73CD5806-5CE4-40A7-957B-8F164E26FAFB@kernel.crashing.org>
On Tue, 2008-04-29 at 18:52 -0500, Kumar Gala wrote:
> On Apr 29, 2008, at 4:28 PM, Paul Mackerras wrote:
> > Kumar Gala writes:
> >
> >> We need to have unique transfer_to_handler paths for each exception
> >> level
> >> that is supported. We need to use the proper xSRR0/1 depending on
> >> which
> >> exception level the interrupt was from. The macro conversion lets up
> >> templatize this code path.
> >
> > It seems to me that this implies you are assuming that you will never
> > ever get a synchronous normal interrupt such as a TLB miss while you
> > are in a critical or machine check handler.
>
> Grr.. one more thing to fix :)
>
> > Wouldn't it be better and safer to have the exception prolog for
> > critical interrupts save SRR0/1 in the stack frame, and have the
> > prolog for machine checks save SRR0/1 and CSRR0/1 likewise?
>
> If we do this I guess we can use SRR0/1 regardless of which level we
> came from.
Also consider saving/restoring MAS
Ben.
next prev parent reply other threads:[~2008-04-30 6:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 13:56 [PATCH] [POWERPC] convert transfer_to_handler into a macro Kumar Gala
2008-04-29 18:35 ` Scott Wood
2008-04-29 19:36 ` Kumar Gala
2008-04-29 19:40 ` Scott Wood
2008-04-29 21:28 ` Paul Mackerras
2008-04-29 23:52 ` Kumar Gala
2008-04-30 3:24 ` Paul Mackerras
2008-04-30 8:00 ` Kumar Gala
2008-04-30 6:32 ` Benjamin Herrenschmidt [this message]
2008-04-30 8:02 ` Kumar Gala
2008-04-30 21:59 ` Benjamin Herrenschmidt
2008-04-30 22:04 ` Kumar Gala
2008-04-30 23:45 ` Josh Boyer
2008-04-30 23:53 ` Benjamin Herrenschmidt
2008-05-01 0:11 ` Josh Boyer
2008-05-01 0:48 ` Benjamin Herrenschmidt
2008-05-01 1:31 ` Kumar Gala
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=1209537128.18023.225.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).