linux-kernel - Re: [RFC][PATCH] signal: replace !likely with unlikely!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <54144672.9060807@roeck-us.net>
Date:	Sat, 13 Sep 2014 06:28:18 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Richard Weinberger <richard@....at>,
	Li RongQing <roy.qing.li@...il.com>
CC:	linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
	fabf@...net.be, jkosina@...e.cz,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>, oleg@...hat.com,
	akpm@...ux-foundation.org
Subject: Re: [RFC][PATCH] signal: replace !likely with unlikely!

On 09/13/2014 03:04 AM, Richard Weinberger wrote:
> Am 13.09.2014 04:48, schrieb Li RongQing:
>> I did not test, how to test it?
>
> Compare the object files of both variants to find out whether both create
> semantically equivalent code and whether the un/likely have an effect.
> i.e. objdump -S -d kernel/signal.o
> I guess you can just remove the likely as gcc is smart enough to detect the "goto ret;"
> as an unlikely taken branch.
>
Or just write similar test code and observe the result.

When you are doing that, you might learn that if "(!likely(expression))"
is _not_ the same as "if (unlikely(!expression))".

Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/