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
| ||
|
Date: Wed, 11 Jul 2012 21:49:46 -0600 From: David Ahern <dsahern@...il.com> To: Jovi Zhang <bookjovi@...il.com> CC: Arnaldo Carvalho de Melo <acme@...stprotocols.net>, Arnaldo Carvalho de Melo <acme@...radead.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] perf: fix perf-lock report coredump On 7/10/12 11:14 PM, Jovi Zhang wrote: >> Does this fix it for you: >> http://lkml.org/lkml/2012/7/6/405 >> > Yeah, same problem. > But the question is if there have some sample event with raw data in > perf.data, are we still just exit(1)? > or let perf-lock only report those sample events with raw data? perf-lock uses 4 tracepoints. tracepoints add -R (raw data) to events. So, if the perf.data does not have tracepoints, there is no need for perf-lock info or report subcommands to proceed. David -- 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/
Powered by blists - more mailing lists