| 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: Mon, 21 Sep 2009 09:36:52 +0200 From: Arjan van de Ven <arjan@...radead.org> To: Steven Rostedt <rostedt@...dmis.org> Cc: linux-kernel@...r.kernel.org, Frederic Weisbecker <fweisbec@...il.com>, mingo@...e.hu Subject: TRACE_EVENT_ABI ? Hi, Ingo suggested to make a TRACE_EVENT_ABI, which is equivalent in implementation to TRACE_EVENT, except that it signals a stable interface. In trying to implement this I'm running into a wall where TRACE_EVENT keeps being defined in many different ways all over the place, making this a really nasty hack to make it just an alias. Do you have any clever ideas on how to make this an alias without fouling up the whole tracing system? -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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