From: Ingo Molnar <mingo@elte.hu>
To: Liming Wang <liming.wang@windriver.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ftrace: adding other non-leaving .text sections
Date: Wed, 26 Nov 2008 03:49:30 +0100 [thread overview]
Message-ID: <20081126024930.GC31342@elte.hu> (raw)
In-Reply-To: <1227666566-9044-1-git-send-email-liming.wang@windriver.com>
* Liming Wang <liming.wang@windriver.com> wrote:
> Please review this patch, and I don't know whether new sections will conflict
> with sched tracer or others.
> This patch is against Steven tree's tip/devel latest commit.
>
> Impact: improve recordmcount.pl
>
> Besides .text section, there are three .text sections that won't
> be freed after kernel booting. They are: .sched.text, .spinlock.text
> and .kprobes.text, which contain functions we can trace. But the last
> section ".kprobes.text" is particular, which has been marked as "notrace",
> we ignore it. Thus we add other two sections.
>
> Signed-off-by: Liming Wang <liming.wang@windriver.com>
> ---
> scripts/recordmcount.pl | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/scripts/recordmcount.pl b/scripts/recordmcount.pl
> index 0197e2f..0b1dc9f 100755
> --- a/scripts/recordmcount.pl
> +++ b/scripts/recordmcount.pl
> @@ -112,6 +112,8 @@ my ($arch, $bits, $objdump, $objcopy, $cc,
> # Acceptable sections to record.
> my %text_sections = (
> ".text" => 1,
> + ".sched.text" => 1,
> + ".spinlock.text" => 1,
> );
make sense - applied to tip/tracing/ftrace, thanks!
Ingo
next prev parent reply other threads:[~2008-11-26 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 2:29 Liming Wang
2008-11-26 2:49 ` Ingo Molnar [this message]
2008-11-26 3:03 ` Steven Rostedt
2008-11-26 3:04 ` Paul Mundt
2008-11-26 3:14 ` walimis
2008-11-26 3:18 ` Paul Mundt
2008-11-26 3:24 ` walimis
2008-11-26 3:20 ` Steven Rostedt
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=20081126024930.GC31342@elte.hu \
--to=mingo@elte.hu \
--cc=liming.wang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®