From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUG] gcov causes vread_tsc to increment kernel memory
Date: Fri, 03 Jul 2009 10:17:07 +0200 [thread overview]
Message-ID: <4A4DBE83.2020803@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090703071315.GE32687@elte.hu>
Ingo Molnar wrote:
> * Peter Oberparleiter <oberpar@linux.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.
prev parent reply other threads:[~2009-07-03 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 16:54 [BUG] gcov causes vread_tsc to increment kernel memory Steven Rostedt
2009-07-02 11:58 ` Peter Oberparleiter
2009-07-02 13:30 ` Steven Rostedt
2009-07-03 7:13 ` Ingo Molnar
2009-07-03 8:17 ` Peter Oberparleiter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4DBE83.2020803@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.