linux-kernel - Re: [PATCH 0/4][RFC] jump label: introduce default true branch

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 20 Feb 2012 14:47:47 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jason Baron <jbaron@...hat.com>
CC:	a.p.zijlstra@...llo.nl, rostedt@...dmis.org,
	mathieu.desnoyers@...icios.com, mingo@...e.hu, davem@...emloft.net,
	ddaney.cavm@...il.com, pjt@...gle.com, rth@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4][RFC] jump label: introduce default true branch

On 12/21/2011 11:09 AM, Jason Baron wrote:
> Hi Peter,
> 
> I've introduced a new static_branch_def_true() construct, such that the straight
> line path is the true branch, and we patch a jump to get to the false branch.
> In order to make jump_label_inc()/dec() work as 'make true'/'make false' with
> counting, I've had to update some of the core jump label code. This patchset also
> introduces: JUMP_LABEL_INIT_TRUE/FALSE, so that keys should be initialized as:
> 
> struct jump_label_key true_key = JUMP_LABEL_INIT_TRUE;
> 
>            or
> 
> struct jump_label_key false_key = JUMP_LABEL_INIT_FALSE;
> 
> I think this patch series should address the issues that came up with sched_feat()
> implementation.
> 

Hi,

Did this ever get addressed?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/