linux-kernel - Re: [rfc] x86,perf: P4 PMU -- use hash for p4_get_escr

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: <1273560424.30322.13.camel@minggr.sh.intel.com>
Date:	Tue, 11 May 2010 14:47:04 +0800
From:	Lin Ming <ming.m.lin@...el.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Cyrill Gorcunov <gorcunov@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [rfc] x86,perf: P4 PMU -- use hash for p4_get_escr_idx

On Tue, 2010-05-11 at 14:41 +0800, Ingo Molnar wrote:
> * Ingo Molnar <mingo@...e.hu> wrote:
> 
> > 
> > * Lin Ming <ming.m.lin@...el.com> wrote:
> > 
> > > On Mon, 2010-05-10 at 23:27 +0800, Cyrill Gorcunov wrote:
> > > > Hi Ming,
> > > > 
> > > > could you give this patch a shot if possible? Compile
> > > > tested only. I would appreciate review and complains
> > > > as well :) I know you're busy with other perf task
> > > > so there is no hurry. Just to share the patch as early
> > > > as possible.
> > > 
> > > Hi, 
> > > 
> > > I'm going to test this patch, but current tip/master(c6661c5) seems has
> > > problem.
> > 
> > Does reverting 4fd38e4595e2f6c9d27732c042a0e16b2753049c help?
> 
> If not then it would be nice if you could try to do a bisection.

Yes, it's the commit 4fd38e45 causes the regression.

> 
> 	Ingo

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