> > > > > > > 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
