From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] recordmcount: arm: Implement make_nop
Date: Tue, 2 Feb 2016 18:25:31 +0100 [thread overview]
Message-ID: <20160202172531.GA9044@debian> (raw)
In-Reply-To: <1454371583-9064-1-git-send-email-sboyd@codeaurora.org>
On Mon, Feb 01, 2016 at 04:06:23PM -0800, Stephen Boyd wrote:
> In similar spirit to x86 and arm64 support, add a make_nop_arm()
> to replace calls to mcount with nops in sections that aren't
> traced.
>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Rabin Vincent <rabin@rab.in>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
>
> Changes from v1:
> * Replace with nops instead of pops
> * Check for BE or LE kernel with elf headers
> * Drop mcount style check because now we look at the previous
> instruction to determine if it's a push (__gnu_mcount_nc) or not (mcount).
Acked-by: Rabin Vincent <rabin@rab.in>
prev parent reply other threads:[~2016-02-02 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 0:06 [PATCH v2] recordmcount: arm: Implement make_nop Stephen Boyd
2016-02-02 17:25 ` Rabin Vincent [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=20160202172531.GA9044@debian \
--to=rabin@rab.in \
--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).