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, 22 Sep 2010 20:30:33 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Ingo Molnar <mingo@...e.hu> Cc: Steven Rostedt <rostedt@...dmis.org>, Arjan van de Ven <arjan@...ux.intel.com>, Jean Pihet <jean.pihet@...oldbits.com>, Thomas Renninger <trenn@...e.de>, Len Brown <len.brown@...el.com>, arjan@...radead.org, Kevin Hilman <khilman@...prootsystems.com>, linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org, linux-omap@...r.kernel.org, linux-perf-users@...r.kernel.org, linux-trace-users@...r.kernel.org Subject: Re: [PATCH] tracing, perf: add more power related events On Wed, 2010-09-22 at 20:23 +0200, Ingo Molnar wrote: > * Steven Rostedt <rostedt@...dmis.org> wrote: > > > We could add a TRACE_EVENT_ABI() as Ingo has been suggesting. [...] > > That would be rather useful. > > We could still be flexible about experimental tracepoints (they dont > hurt), but apps should stick to ABI bits - or at least not complain when > non-ABI tracepoints change for good reasons. (arbitrary, avoidable > changes are still bad obviously, regardless of the type of the > tracepoint) > > We'd be more stringent with marking tracepoints an ABI. > > So yes, this would be lovely to have. Why? As long as we mandate that apps need to fully parse the format stuff anyway, it doesn't buy us much. -- 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