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 2/3] powerpc: Use MSR_64BIT in places
Date: Sun, 10 Apr 2011 08:04:41 +1000 [thread overview]
Message-ID: <1302386681.28876.0.camel@pasglop> (raw)
In-Reply-To: <FA53E865-AB9E-4222-A990-F552E1A1C093@kernel.crashing.org>
On Fri, 2011-04-08 at 04:24 -0500, Kumar Gala wrote:
> On Apr 8, 2011, at 2:56 AM, Michael Ellerman wrote:
>
> > Use the new MSR_64BIT in a few places. Some of these are already ifdef'ed
> > for BOOKE vs BOOKS, but it's still clearer, MSR_SF does not immediately
> > parse as "MSR bit for 64bit".
> >
> > Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> > ---
> > arch/powerpc/kernel/head_64.S | 2 +-
> > arch/powerpc/kernel/signal_64.c | 4 ++--
> > arch/powerpc/kernel/traps.c | 2 +-
> > arch/powerpc/xmon/xmon.c | 14 +++++++-------
> > 4 files changed, 11 insertions(+), 11 deletions(-)
>
> However MSR_ISF does ;)
I'm not sure I parse that one :-) Any ways ISF is "interrupt SF" and has
no equivalent in the MSR for BookE (it's elsewhere, EPCR no ?).
Cheers,
Ben.
next prev parent reply other threads:[~2011-04-09 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 7:56 [PATCH 1/3] powerpc: Add MSR_64BIT Michael Ellerman
2011-04-08 7:56 ` [PATCH 2/3] powerpc: Use MSR_64BIT in places Michael Ellerman
2011-04-08 9:24 ` Kumar Gala
2011-04-09 22:04 ` Benjamin Herrenschmidt [this message]
2011-04-10 17:29 ` Kumar Gala
2011-04-10 22:00 ` Benjamin Herrenschmidt
2011-04-08 7:56 ` [PATCH 3/3] powerpc: Use MSR_64BIT in sstep.c, fix kprobes on BOOK3E 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=1302386681.28876.0.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).