| 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, 03 Jul 2009 10:17:07 +0200 From: Peter Oberparleiter <oberpar@...ux.vnet.ibm.com> To: Ingo Molnar <mingo@...e.hu> CC: Steven Rostedt <rostedt@...dmis.org>, LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [BUG] gcov causes vread_tsc to increment kernel memory Ingo Molnar wrote: > * Peter Oberparleiter <oberpar@...ux.vnet.ibm.com> wrote: > >> Also seeing as function tracer and gcov work on a similar basis >> and require similar files to be excluded from profiling, it would >> be nice if we wouldn't need to mark those files separately. [...] > > One of the general things i pointed out during review is that > there's a fair amount of overlap between tracing/instrumentation and > the gcov support patches and now for a change Andrew has merged > incomplete stuff upstream prematurely ;-) Yes there is overlap between ftrace and gcov and I will help in finding and merging those bits, but as I also pointed out during review, there are also fundamental differences. By including the gcov infrastructure upstream now, we can incrementally improve its integration with any similar mechanism _while_ people are improving their test cases and identifying more bugs based on code coverage measurements. -- 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