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, 23 Jul 2008 06:13:10 -0400 From: Christoph Hellwig <hch@...radead.org> To: Avi Kivity <avi@...ranet.com> Cc: Christoph Hellwig <hch@...radead.org>, Peter Zijlstra <peterz@...radead.org>, Jan Kiszka <jan.kiszka@...mens.com>, Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>, akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org, kvm@...r.kernel.org, "Feng(Eric) Liu" <eric.e.liu@...el.com> Subject: Re: [patch 4/4] KVM-trace port to tracepoints On Wed, Jul 23, 2008 at 01:08:41PM +0300, Avi Kivity wrote: > trace_mark() is implement kvmtrace, which is propagated to userspace. > So while trace_mark() itself is not a userspace interface, one of its > users is. > > It's an unstable interface. But so is dmesg; that's the nature of tracing. Trace_mark is as stable as any other kernel interface, and the data you pass through it is as stable as you want it to. In most cases like kvmtrace or my spu scheduler tracing code the trace data is directly forwarded through a userspace interface, and that is as stable as any freeform interface, e.g. as like printk mentioned above. -- 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