On Jan 25, 2011, at 12:02 AM, Liu Yu wrote:
> This errata can occur if a single-precision floating-point, double-precision
> floating-point or vector floating-point instruction on a mispredicted branch
> path signals one of the floating-point data interrupts which are enabled by
> the
> SPEFSCR
On Jan 25, 2011, at 12:02 AM, Liu Yu wrote:
> This errata can occur if a single-precision floating-point, double-precision
> floating-point or vector floating-point instruction on a mispredicted branch
> path signals one of the floating-point data interrupts which are enabled by
> the
> SPEFSCR
> -Original Message-
> From: Gala Kumar-B11780
> Sent: Tuesday, January 25, 2011 3:01 PM
> To: Liu Yu-B13201
> Cc: linuxppc-dev@lists.ozlabs.org; Gala Kumar-B11780
> Subject: Re: [PATCH] e500: Erratum cpu a005 workaround
>
>
> On Jan 25, 2011, at 12:02 AM
> >
> > This isn't the way to do this. We normally add entries in
> > cputable.c an add a new cpu_feature_bit for the errata.
> >
> > Than above we'd do:
> >
> > if (cur_cpu_spec->cpu_features & CPU_FTR_E500_A005_ERRATUM)
> >
> >
>
> IMHO, a cpu erratum is not a cpu feature.
> See there're
