linux-kernel - Re: Final per cpu consistency patch for -next or late in 3.19 merge period

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]

Message-ID: <alpine.DEB.2.11.1412021150460.19228@gentwo.org>
Date:	Tue, 2 Dec 2014 11:51:33 -0600 (CST)
From:	Christoph Lameter <cl@...ux.com>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
cc:	Tejun Heo <htejun@...il.com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Final per cpu consistency patch for -next or late in 3.19 merge
 period

On Tue, 2 Dec 2014, Mathieu Desnoyers wrote:

> If I understand correctly, __get_cpu_var() is being deprecated ?

Its gone in -next.

> If this_cpu_ptr() is semantically equivalent to __get_cpu_var(), we can do a
> wrapper in lttng-modules and move to the new name, no worries there.

Sure. Look at the conversion descriptions.

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