From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Michael Ellerman <mpe@ellerman.id.au>, CGEL <cgel.zte@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Sandipan Das <sandipan@linux.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Zeal Robot <zealci@zte.com.cn>, Jing Yangyang <jing.yangyang@zte.com.cn>
Subject: Re: [PATCH linux-next] power:pkeys: fix bugon.cocci warnings
Date: Sat, 7 May 2022 07:04:01 +0000 [thread overview]
Message-ID: <e2310273-8bc8-deac-9a80-0d1587acecb1@csgroup.eu> (raw)
In-Reply-To: <8735hsvzig.fsf@mpe.ellerman.id.au>
Le 02/05/2022 à 15:24, Michael Ellerman a écrit :
> CGEL <cgel.zte@gmail.com> writes:
>> From: Jing Yangyang <jing.yangyang@zte.com.cn>
>>
>> Use BUG_ON instead of a if condition followed by BUG.
>>
>> ./arch/powerpc/include/asm/book3s/64/pkeys.h:21:2-5:WARNING
>> Use BUG_ON instead of if condition followed by BUG.
>> ./arch/powerpc/include/asm/book3s/64/pkeys.h:14:2-5:WARNING
>> Use BUG_ON instead of if condition followed by BUG.
>>
>> Generated by: scripts/coccinelle/misc/bugon.cocci
>>
>> Reported-by: Zeal Robot <zealci@zte.com.cn>
>> Signed-off-by: Jing Yangyang <jing.yangyang@zte.com.cn>
>> ---
>> arch/powerpc/include/asm/book3s/64/pkeys.h | 6 ++----
>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/powerpc/include/asm/book3s/64/pkeys.h b/arch/powerpc/include/asm/book3s/64/pkeys.h
>> index 5b17813..5f74f0c 100644
>> --- a/arch/powerpc/include/asm/book3s/64/pkeys.h
>> +++ b/arch/powerpc/include/asm/book3s/64/pkeys.h
>> @@ -10,15 +10,13 @@ static inline u64 vmflag_to_pte_pkey_bits(u64 vm_flags)
>> if (!mmu_has_feature(MMU_FTR_PKEY))
>> return 0x0UL;
>>
>> - if (radix_enabled())
>> - BUG();
>> + BUG_ON(radix_enabled());
>> return hash__vmflag_to_pte_pkey_bits(vm_flags);
>> }
>>
>> static inline u16 pte_to_pkey_bits(u64 pteflags)
>> {
>> - if (radix_enabled())
>> - BUG();
>> + BUG_ON(radix_enabled());
>> return hash__pte_to_pkey_bits(pteflags);
>> }
>
> Have you checked how this changes the generated code?
>
> radix_enabled() is a jump label, via mmu_feature().
>
> Possibly the compiler just works it all out and generates the same code,
> but I'd want some evidence of that before merging this.
Seems like the compiler is not that good, the generated code for test1()
is much better than the one for test2(), see below.
void test1(void)
{
if (radix_enabled())
BUG();
}
void test2(void)
{
BUG_ON(radix_enabled());
}
0000000000000900 <.test1>:
900: 60 00 00 00 nop
904: 0f e0 00 00 twui r0,0
908: 60 00 00 00 nop
90c: 60 00 00 00 nop
910: 4e 80 00 20 blr
914: 60 00 00 00 nop
918: 60 00 00 00 nop
91c: 60 00 00 00 nop
0000000000000920 <.test2>:
920: 60 00 00 00 nop
924: 39 20 00 01 li r9,1
928: 0b 09 00 00 tdnei r9,0
92c: 4e 80 00 20 blr
930: 39 20 00 00 li r9,0
934: 0b 09 00 00 tdnei r9,0
938: 4e 80 00 20 blr
We should keep things as they are and change the coccinelle script.
Christophe
next prev parent reply other threads:[~2022-05-07 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 6:42 CGEL
2021-08-31 6:01 ` Daniel Axtens
2022-05-02 13:24 ` Michael Ellerman
2022-05-07 7:04 ` Christophe Leroy [this message]
2022-05-07 8:49 ` Arnd Bergmann
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=e2310273-8bc8-deac-9a80-0d1587acecb1@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=benh@kernel.crashing.org \
--cc=cgel.zte@gmail.com \
--cc=jing.yangyang@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sandipan@linux.ibm.com \
--cc=zealci@zte.com.cn \
/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
all inboxes | Powered by JetHome®