linux-kernel - Re: [PATCH 05/10] perf, tools, stat: Basic support for TopDown in perf stat

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:	Thu, 17 Dec 2015 15:03:58 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Jiri Olsa <jolsa@...nel.org>, Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 05/10] perf, tools, stat: Basic support for TopDown in
 perf stat

> >> This is x86 specific. Why not just try it out and in case of error
> >> suggest checking
> >> if pinned system-wide events exist (such as NMI watchdog on x86). that would
> >> be more generic.
> >
> > That's really complicated, i would have to tear down all state and then
> > resubmit all the events. I think just checking the NMI watchdog is good
> > enough. I couldn't give a sensible error message for the generic case
> > anyways.
> >
> What about that fancy error reporting extension that was proposed a few months
> back? It could help print a sensible error msg. Did it ever make it in?

AFAIK it's not in. Also even the extended error wouldn't know who
installed a pinned counter.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/