linux-kernel - Re: perf user tool precise attribute broken in 3.5rc1+

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:	Fri, 8 Jun 2012 12:48:14 -0300
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Stephane Eranian <eranian@...gle.com>, jolsa@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: perf user tool precise attribute broken in 3.5rc1+

Em Fri, Jun 08, 2012 at 05:10:09AM +0200, Andi Kleen escreveu:
> > Are you sure the old one works? Perhaps it silently falls back to
> > cpu-clock?
 
> Yes i'm sure. I was actually debugging some kernel pebs code,
> and had a heavily instrumented pebs code path and was first trying
> to figure out what went wrong in the kernel, until I realized 
> that the userland was broken.
> 
> Does :p work for anyone else?

It seems to work for Linus on Ivy Bridge with what is on tip/perf/urgent
 
> BTW I hope the perf userland becomes more stable again. Recently I've had
> far more trouble with the user binary than the kernel driver, which
> is unusal.

Well, as a feedback your post is very much appreciated, we'll try to do
better.

What areas do you feel are more troubling? Anything you reported that
still hasn't been fixed?

Probably we should stop working on features and just process patches and
work on a suite of autotest scripts, something we've been discussing but
not working that much at.

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