From: Oliver <oohall@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/asm: Mark cr0 as clobbered in mftb()
Date: Tue, 11 Jul 2017 14:02:51 +1000 [thread overview]
Message-ID: <CAOSf1CE6dpSO2WA8WmE=gXEoRfKg2OgQwDnhnWt_68NaHTXTdQ@mail.gmail.com> (raw)
In-Reply-To: <8737a4v7dd.fsf@concordia.ellerman.id.au>
On Mon, Jul 10, 2017 at 9:50 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> Oliver O'Halloran <oohall@gmail.com> writes:
>
>> The workaround for the CELL timebase bug does not correctly mark cr0 as
>> being clobbered. This can result in GCC making some poor^W completely
>> broken optimisations.
>
> Fruit 'n oats, how did we never notice that? Luck I guess. Or subtle
> breakage that no one could pin down :E
Dumb luck probably. The workaround is inside a feature section which
depends on CPU_FTR_CELL_TB_BUG so you would only ever see a problem
when actually running on Cell (can't be that many people...). CR0
being volatile across function calls probably helped mask it too.
> I'll tag it for stable.
Good idea.
> Your change log is not entirely fair, it's not GCC's fault, we changed
> register state without telling it, so it's on us :) I'll reword it a
> bit here.
Yeah that was probably a bit harsh.
>
> cheers
>
>> diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h
>> index 7e50e47375d6..a3b6575c7842 100644
>> --- a/arch/powerpc/include/asm/reg.h
>> +++ b/arch/powerpc/include/asm/reg.h
>> @@ -1303,7 +1303,7 @@ static inline void msr_check_and_clear(unsigned long bits)
>> " .llong 0\n" \
>> ".previous" \
>> : "=r" (rval) \
>> - : "i" (CPU_FTR_CELL_TB_BUG), "i" (SPRN_TBRL)); \
>> + : "i" (CPU_FTR_CELL_TB_BUG), "i" (SPRN_TBRL) : "cr0"); \
>> rval;})
>> #else
>> #define mftb() ({unsigned long rval; \
>> --
>> 2.9.4
next prev parent reply other threads:[~2017-07-11 4:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 8:46 [PATCH] powerpc/asm: Mark cr0 as clobbered in mftb() Oliver O'Halloran
2017-07-10 11:50 ` Michael Ellerman
2017-07-10 13:43 ` Segher Boessenkool
2017-07-11 2:33 ` Michael Ellerman
2017-07-11 4:02 ` Oliver [this message]
2017-07-11 12:48 ` 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='CAOSf1CE6dpSO2WA8WmE=gXEoRfKg2OgQwDnhnWt_68NaHTXTdQ@mail.gmail.com' \
--to=oohall@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).