Re: [PATCH -v2 6/8] jump_label: Add a new static_key interface

From: Heiko Carstens
Date: Wed Jul 29 2015 - 02:43:39 EST


On Tue, Jul 28, 2015 at 03:21:01PM +0200, Peter Zijlstra wrote:
> There are various problems and short-comings with the current
> static_key interface:
>
> - static_key_{true,false}() read like a branch depending on the key
> value, instead of the actual likely/unlikely branch depending on
> init value.
>
> - static_key_{true,false}() are, as stated above, tied to the
> static_key init values STATIC_KEY_INIT_{TRUE,FALSE}.
>
> - we're limited to the 2 (out of 4) possible options that compile to
> a default NOP because that's what our arch_static_branch() assembly
> emits.
>
> So provide a new static_key interface:
>
> DEFINE_STATIC_KEY_TRUE(name);
> DEFINE_STATIC_KEY_FALSE(name);
>
> Which define a key of different types with an initial true/false
> value.
>
> Then allow:
>
> static_branch_likely()
> static_branch_unlikely()
>
> to take a key of either type and emit the right instruction for the
> case.
>
> This means adding a second arch_static_branch_jump() assembly helper
> which emits a JMP per default.
>
> In order to determine the right instruction for the right state,
> encode the branch type in the LSB of jump_entry::key.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@xxxxxxxxxxxxx>
> ---
> arch/arm/include/asm/jump_label.h | 24 +++--
> arch/arm64/include/asm/jump_label.h | 18 +++-
> arch/mips/include/asm/jump_label.h | 19 ++++
> arch/powerpc/include/asm/jump_label.h | 19 ++++
> arch/s390/include/asm/jump_label.h | 19 ++++
> arch/sparc/include/asm/jump_label.h | 35 ++++++--
> arch/x86/include/asm/jump_label.h | 21 ++++
> include/linux/jump_label.h | 143 ++++++++++++++++++++++++++++++++--
> kernel/jump_label.c | 35 ++++++--
> 9 files changed, 294 insertions(+), 39 deletions(-)

for the s390 part:

Acked-by: Heiko Carstens <heiko.carstens@xxxxxxxxxx>

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