| 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: Fri, 17 Jun 2011 08:28:44 -0600 From: David Ahern <dsahern@...il.com> To: Frederic Weisbecker <fweisbec@...il.com> CC: linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org, acme@...stprotocols.net, mingo@...e.hu, peterz@...radead.org, paulus@...ba.org, tglx@...utronix.de Subject: Re: [PATCH 3/6] perf: add reference time event On 06/17/2011 08:17 AM, Frederic Weisbecker wrote: >>> We would like to avoid adding more custom events like these. They were very convenient >>> but they steal the kernel event type space. They are deemed for removal in the long term. >>> >>> Another idea to achieve what you want would be to create a new perf event header feature, >>> like HEADER_TRACE_INFO or HEADER_BUILD_ID are. Then use that to create a space in the perf >>> file to save that couple of clocks initial values. >> >> you mean like this: >> https://lkml.org/lkml/2010/12/7/813 >> >> David > > Exactly, why did you change? As I recall suggestions on adding new clock events and using those for periodic samples. Once we have the initial correlation (the point of this patch) and updates to xtime (the new tracepoints) periodic events should not be needed. I'll go back to this option -- and address comments from that round as well. 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