From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Fix 44x Machine Check handling
Date: Sat, 17 Nov 2007 09:21:41 +1100 [thread overview]
Message-ID: <1195251702.28865.182.camel@pasglop> (raw)
In-Reply-To: <6612E7C6-C570-4748-BCEE-AC6733C0BB14@kernel.crashing.org>
> > Index: linux-work/include/asm-powerpc/cputable.h
> > ===================================================================
> > --- linux-work.orig/include/asm-powerpc/cputable.h 2007-11-16
> > 16:14:29.000000000 +1100
> > +++ linux-work/include/asm-powerpc/cputable.h 2007-11-16
> > 16:19:35.000000000 +1100
> > @@ -138,6 +138,7 @@ extern void do_feature_fixups(unsigned l
> > #define CPU_FTR_FPU_UNAVAILABLE ASM_CONST(0x0000000000800000)
> > #define CPU_FTR_UNIFIED_ID_CACHE ASM_CONST(0x0000000001000000)
> > #define CPU_FTR_SPE ASM_CONST(0x0000000002000000)
> > +#define CPU_FTR_440A ASM_CONST(0x0000000004000000)
>
> Can we be more specific about what this feature really means.
>
> How about something like CPU_FTR_ENH_MCHCK or something like that.
Did that at first, then figured out that I indeed had 2 core manuals one
of them being labelled "A"... I'm trying to figure out what other
differences they may have to see whether I should stick to that CPU
feature or just remove it completely and do as Olof suggested.
Ben.
prev parent reply other threads:[~2007-11-16 22:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 7:21 [PATCH] powerpc: Fix 44x Machine Check handling Benjamin Herrenschmidt
2007-11-16 7:40 ` Olof Johansson
2007-11-16 7:41 ` Benjamin Herrenschmidt
2007-11-16 7:45 ` Benjamin Herrenschmidt
2007-11-16 21:55 ` Kumar Gala
2007-11-17 17:09 ` Josh Boyer
2007-11-16 14:58 ` Josh Boyer
2007-11-16 21:03 ` Benjamin Herrenschmidt
2007-11-16 21:54 ` Kumar Gala
2007-11-16 22:21 ` Benjamin Herrenschmidt [this message]
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=1195251702.28865.182.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@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).