From: Ingo Molnar <mingo@elte.hu>
To: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
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, 3 Jul 2009 09:13:15 +0200 [thread overview]
Message-ID: <20090703071315.GE32687@elte.hu> (raw)
In-Reply-To: <4A4CA0D5.6010103@linux.vnet.ibm.com>
* 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 ;-) Andrew, could you please
make sure this all gets fixed and the review suggestions get
implemented?
Ingo
next prev parent reply other threads:[~2009-07-03 7:13 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 [this message]
2009-07-03 8:17 ` Peter Oberparleiter
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=20090703071315.GE32687@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oberpar@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox