From: Scott Wood <scottwood@freescale.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] powerpc: Decode correct MSR bits in oops output
Date: Mon, 28 Nov 2011 14:32:25 -0600 [thread overview]
Message-ID: <4ED3EFD9.9010200@freescale.com> (raw)
In-Reply-To: <CA+5PVA75TKyScsPfHXXPaHC3mobPRJ0_w48HGRJ1j_-7ktP3iA@mail.gmail.com>
On 11/28/2011 02:12 PM, Josh Boyer wrote:
> On Mon, Nov 28, 2011 at 3:04 PM, Scott Wood <scottwood@freescale.com> wrote:
>> On 11/28/2011 01:46 PM, Josh Boyer wrote:
>>> Could introduce BOOK3E_32 to cover cases like this.
>>
>> Why _32? These bits apply to 64-bit as well. MSR_CM is only for 64-bit.
>
> Because CONFIG_BOOK3E depeonds on PPC_BOOK3E_64. So either that
> dependency needs to go so it's selectable elsewhere, or a similarly
> intended PPC_BOOK3E_32 needs to get created. Or something.
I think that dependency should go, in any case. We already have
PPC_BOOK3E_64 for places that need to depend on that, and we don't want
to end up having this all over the place:
#if defined(CONFIG_PPC_BOOK3E_32) || defined(CONFIG_PPC_BOOK3E_64)
>> UCLE and PMM are present on pre-2.06 e500 cores as well.
>
> Sigh. Maybe there is no way to get un-ugly.
If we drop the 64-bit dependency, we could do this for UCLE if it really
needs to be omitted from a 4xx kernel:
#if defined(CONFIG_PPC_BOOK3E) || defined(CONFIG_E500)
PMM is not just a BookE thing, so if 4xx really needs to exclude it,
#ifndef CONFIG_4xx is the way to go.
I wouldn't bother unless 4xx is known to set these bits, though.
For GS and CM CONFIG_PPC_BOOK3E is OK, once 32-bit e500mc/e5500 kernels
start selecting it.
-Scott
next prev parent reply other threads:[~2011-11-28 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 5:35 [PATCH] powerpc: Decode correct MSR bits in oops output Anton Blanchard
2011-11-28 16:04 ` Kumar Gala
2011-11-28 16:23 ` Josh Boyer
2011-11-28 19:30 ` Scott Wood
2011-11-28 19:46 ` Josh Boyer
2011-11-28 20:04 ` Scott Wood
2011-11-28 20:12 ` Josh Boyer
2011-11-28 20:32 ` Scott Wood [this message]
2011-11-28 20:40 ` 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=4ED3EFD9.9010200@freescale.com \
--to=scottwood@freescale.com \
--cc=anton@samba.org \
--cc=jwboyer@gmail.com \
--cc=linuxppc-dev@lists.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).