From: Paul Mundt <lethal@linux-sh.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Liming Wang <liming.wang@windriver.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ftrace: adding other non-leaving .text sections
Date: Wed, 26 Nov 2008 12:04:46 +0900 [thread overview]
Message-ID: <20081126030446.GA14685@linux-sh.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0811252201270.26424@gandalf.stny.rr.com>
On Tue, Nov 25, 2008 at 10:03:35PM -0500, Steven Rostedt wrote:
>
> On Wed, 26 Nov 2008, Liming Wang 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.
>
> Yep, only those sections that we know will not disappear are OK. I was
> conservative with only using ".text" but I knew there were other sections
> that were OK, so I used the hash array to make it easy to add others.
>
Does your .text cover .text.head by the way?
next prev parent reply other threads:[~2008-11-26 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 2:29 [PATCH 1/1] ftrace: adding other non-leaving .text sections Liming Wang
2008-11-26 2:49 ` Ingo Molnar
2008-11-26 3:03 ` Steven Rostedt
2008-11-26 3:04 ` Paul Mundt [this message]
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=20081126030446.GA14685@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=liming.wang@windriver.com \
--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.