| 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
| ||
|
Message-Id: <20070502094707.4197ab7a.akpm@linux-foundation.org> Date: Wed, 2 May 2007 09:47:07 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Andi Kleen <andi@...stfloor.org> Cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>, linux-kernel@...r.kernel.org, rusty@...tcorp.com.au, wfg@...c.edu Subject: Re: 2.6.22 -mm merge plans On Wed, 2 May 2007 12:44:13 +0200 Andi Kleen <andi@...stfloor.org> wrote: > > It is currently used as an instrumentation infrastructure for the LTTng > > tracer at IBM, Google, Autodesk, Sony, MontaVista and deployed in > > WindRiver products. The SystemTAP project also plan to use this type of > > infrastructure to trace sites hard to instrument. The Linux Kernel > > Markers has the support of Frank C. Eigler, author of their current > > marker alternative (which he wishes to drop in order to adopt the > > markers infrastructure as soon as it hits mainline). > > All of the above don't use mainline kernels. That's because they have to add a markers patch! > That doesn't constitute using it. Andi, there was a huge amount of discussion about all this in September last year (subjects: *markers* and *LTTng*). The outcome of all that was, I believe, that the kernel should have a static marker infrastructure. - 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