From: kzak@redhat.com (Karel Zak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] util-linux: readprofile: don't stop parsing at __init_end
Date: Tue, 12 Apr 2011 12:11:35 +0200 [thread overview]
Message-ID: <20110412101135.GA7869@nb.net.home> (raw)
In-Reply-To: <1302255353-1622-1-git-send-email-ratbert.chuang@gmail.com>
On Fri, Apr 08, 2011 at 05:35:53PM +0800, Po-Yu Chuang wrote:
> From: Po-Yu Chuang <ratbert@faraday-tech.com>
>
> Some architectures like ARM place __init_end before .text section.
> If any function in .init section is hit while profiling, readprofile
> stops at __init_end. That means if we enable profiling at boot time,
> the profiler probably hits init functions and readprofile does not
> work well unless we reset profiling buffer with -r option.
>
> Signed-off-by: Po-Yu Chuang <ratbert@faraday-tech.com>
> ---
> sys-utils/readprofile.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
Applied, thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2011-04-12 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 9:35 [PATCH RFC] util-linux: readprofile: don't stop parsing at __init_end Po-Yu Chuang
2011-04-12 10:11 ` Karel Zak [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=20110412101135.GA7869@nb.net.home \
--to=kzak@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).