linux-kernel - RE: [PATCHv3 00/56] perf stat: Add scripting support

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: <37D7C6CF3E00A74B8858931C1DB2F0770196ED30@SHSMSX103.ccr.corp.intel.com>
Date:	Fri, 9 Oct 2015 18:31:23 +0000
From:	"Liang, Kan" <kan.liang@...el.com>
To:	Jiri Olsa <jolsa@...hat.com>
CC:	Jiri Olsa <jolsa@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Andi Kleen <andi@...stfloor.org>,
	Ulrich Drepper <drepper@...il.com>,
	"Will Deacon" <will.deacon@....com>,
	Stephane Eranian <eranian@...gle.com>,
	"Don Zickus" <dzickus@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>,
	"David Ahern" <dsahern@...il.com>, Ingo Molnar <mingo@...nel.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: RE: [PATCHv3 00/56] perf stat: Add scripting support



> 
> >
> >
> > 3. I think you have already handled new record type for perf stat record.
> > But the "unhandled!" message still show in the perf report -D.
> >
> > 0x598 [0x30]: PERF_RECORD_STAT
> > ... id 22385, cpu 0, thread 0
> > ... value 1752, enabled 501473097, running 501473097
> > : unhandled!      <-------
> 
> yep, I was wondering about that as well.. but it's not 'handled' in perf
> report, it just displays the raw output of the event.. but I think we could
> remove that not to confuse
> 
> and perhaps we could also add -D for perf stat report

Agree.

> 
> >
> >
> > 4. Core dump when applying --per-core -a for stat record.
> >
> > sudo ./perf stat -e 'cycles' --per-core -a record sleep 1
> >
> > ** Error in `./perf': corrupted double-linked list: 0x00000000036eb560
> > ** ======= Backtrace: ========= /lib64/libc.so.6[0x3002e7bbe7]
> > /lib64/libc.so.6[0x3002e7d2b5] ./perf(perf_env__exit+0xfd)[0x484d1d]
> > ./perf[0x47c45f]
> > ./perf(main+0x610)[0x421ac0]
> > /lib64/libc.so.6(__libc_start_main+0xf5)[0x3002e21b45]
> > ./perf[0x421bd9]
> 
> could not reproduce this one.. any chance you could compile with
> DEBUG=1 and re-run in gdb for more details? like which of the frees got
> crazy.. ?
>
The crash is not caused by this patch set. It's also a bug in current perf.
I've submitted a patch for that.
https://lkml.org/lkml/2015/10/9/575

Thanks,
Kan


 

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