[PATCH] nx-842: Ignore bit 3 of condition register returned by icswx
Ram Pai
linuxram at us.ibm.com
Tue Nov 3 05:41:17 AEDT 2015
On Mon, Nov 02, 2015 at 12:23:36PM +1100, Michael Ellerman wrote:
> On Fri, 2015-10-30 at 15:31 -0700, Ram Pai wrote:
> > icswx occasionally under heavy load sets bit 3 of condition register 0.
>
> Why?
The hardware manual says that bit is undefined, though it is set under some conditions.
>
> Also you seem to be using IBM bit numbering, so please be explicit about that,
> or use normal bit numbering.
Ok.
>
> > It has no software implication.
>
> What does it mean? You might be right but you don't give me enough info to
> decide.
The software is not supposed to interpret the bit since its meaning is
undefined.
>
> > Currently that bit is interpreted by the driver as a failure, when
> > it should have calmly ignored it.
>
> Should the fix be in icswx or the driver? Please justify your choice.
Yes there are two solutions. One is icswx macro should not expose that
bit to its consumers. Or the driver/consumers can ignore that bit. I
think it makes more sense to contain it in one place, which is icswx
instruction. Drivers or whoever calls icswx should not know
more than what they need to know. This patch uses the first approach.
>
> This sounds like it's fixing a bug so shouldn't the patch go to stable? And if
> so which version(s) should it apply to?
It should go to stable v4.2. I will tag it to stable, in my next
version.
RP
More information about the Linuxppc-dev
mailing list