From: Michael Ellerman <michael@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/4] powerpc: Rename and flesh out the facility unavailable exception handler
Date: Fri, 28 Jun 2013 00:16:31 +1000 [thread overview]
Message-ID: <20130627141631.GA13867@concordia> (raw)
In-Reply-To: <20130627140539.5ff63bad1e7e99e5526d0f3d@canb.auug.org.au>
On Thu, Jun 27, 2013 at 02:05:39PM +1000, Stephen Rothwell wrote:
> Hi Michael,
>
> On Tue, 25 Jun 2013 17:47:56 +1000 Michael Ellerman <michael@ellerman.id.au> wrote:
> >
> > -void tm_unavailable_exception(struct pt_regs *regs)
> > +void facility_unavailable_exception(struct pt_regs *regs)
> > {
> > + static char *facility_strings[] = {
> > + "FPU",
> > + "VMX/VSX",
> > + "DSCR",
> > + "PMU SPRs",
> > + "BHRB",
> > + "TM",
> > + "AT",
> > + "EBB",
> > + "TAR",
> > + };
>
> Are the indexes into this array defined somewhere? If not, can we do
> that. Then, can we use explicit indexed initialisers for this array?
I'm not sure I follow.
The mapping is defined by the definition of the "Interruption Cause"
field of the FSCR, section 6.2.10 of PowerISA v2.07.
cheers
next prev parent reply other threads:[~2013-06-27 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 7:47 [PATCH 1/4] powerpc: Remove unreachable relocation on exception handlers Michael Ellerman
2013-06-25 7:47 ` [PATCH 2/4] powerpc: Remove KVMTEST from RELON " Michael Ellerman
2013-06-25 7:47 ` [PATCH 3/4] powerpc: Rename and flesh out the facility unavailable exception handler Michael Ellerman
2013-06-27 4:05 ` Stephen Rothwell
2013-06-27 14:16 ` Michael Ellerman [this message]
2013-06-28 4:52 ` Stephen Rothwell
2013-06-25 7:47 ` [PATCH 4/4] powerpc: Wire up the HV facility unavailable exception Michael Ellerman
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=20130627141631.GA13867@concordia \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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).