linux-kernel - Re: [PATCH 0/4] convert perf to local64

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: <1274868670.5882.5189.camel@twins>
Date:	Wed, 26 May 2010 12:11:10 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	David Miller <davem@...emloft.net>,
	Paul Mundt <lethal@...ux-sh.org>,
	Will Deacon <will.deacon@....com>,
	Deng-Cheng Zhu <dengcheng.zhu@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] convert perf to local64_t

On Wed, 2010-05-26 at 12:08 +0200, Frederic Weisbecker wrote:
> On Fri, May 21, 2010 at 03:42:05PM +0200, Peter Zijlstra wrote:
> > These patches introduce local64_t.
> > 
> > Since perf_event:count is only modified cross-cpu when child-counters
> > feed back their changes on exit, and we can use a secondary variable
> > for that, we can convert perf to use local64_t instead of atomic64_t
> > and use instructions without buslock semantics.
> > 
> > The local64_t implementation uses local_t for 64 bits, since local_t is
> > of type long, for 32 bit it falls back to atomic64_t. Architectures can
> > provide their own implementation as usual.
> 
> 
> It seems nobody disagrees with it. Can we give it a try?

I'll push it to mingo around -rc2 or so, to let the dust settle from the
current merge.
--
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/