From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] recordmcount: arm64: replace the ignored mcount call into nop
Date: Wed, 28 Oct 2015 11:58:25 +0000 [thread overview]
Message-ID: <20151028115825.GB29512@arm.com> (raw)
In-Reply-To: <20151028041619.4e44491a@grimm.local.home>
On Wed, Oct 28, 2015 at 04:16:19AM -0400, Steven Rostedt wrote:
> On Wed, 28 Oct 2015 16:04:05 +0800
> Li Bin <huawei.libin@huawei.com> wrote:
>
> > By now, the recordmcount only records the function that in
> > following sections:
> > .text/.ref.text/.sched.text/.spinlock.text/.irqentry.text/
> > .kprobes.text/.text.unlikely
> >
> > For the function that not in these sections, the call mcount
> > will be in place and not be replaced when kernel boot up. And
> > it will bring performance overhead, such as do_mem_abort (in
> > .exception.text section). This patch make the call mcount to
> > nop for this case in recordmcount.
>
> I can take this in my tree with an Ack from the ARM64 maintainers.
Looks like it does what it says on the tin:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Li Bin <huawei.libin@huawei.com>,
catalin.marinas@arm.com, takahiro.akashi@linaro.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, guohanjun@huawei.com,
dingtianhong@huawei.com, zhouchengming1@huawei.com
Subject: Re: [PATCH] recordmcount: arm64: replace the ignored mcount call into nop
Date: Wed, 28 Oct 2015 11:58:25 +0000 [thread overview]
Message-ID: <20151028115825.GB29512@arm.com> (raw)
In-Reply-To: <20151028041619.4e44491a@grimm.local.home>
On Wed, Oct 28, 2015 at 04:16:19AM -0400, Steven Rostedt wrote:
> On Wed, 28 Oct 2015 16:04:05 +0800
> Li Bin <huawei.libin@huawei.com> wrote:
>
> > By now, the recordmcount only records the function that in
> > following sections:
> > .text/.ref.text/.sched.text/.spinlock.text/.irqentry.text/
> > .kprobes.text/.text.unlikely
> >
> > For the function that not in these sections, the call mcount
> > will be in place and not be replaced when kernel boot up. And
> > it will bring performance overhead, such as do_mem_abort (in
> > .exception.text section). This patch make the call mcount to
> > nop for this case in recordmcount.
>
> I can take this in my tree with an Ack from the ARM64 maintainers.
Looks like it does what it says on the tin:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2015-10-28 11:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 8:04 [PATCH] recordmcount: arm64: replace the ignored mcount call into nop Li Bin
2015-10-28 8:04 ` Li Bin
2015-10-28 8:16 ` Steven Rostedt
2015-10-28 8:16 ` Steven Rostedt
2015-10-28 11:58 ` Will Deacon [this message]
2015-10-28 11:58 ` Will Deacon
2015-10-29 5:43 ` AKASHI Takahiro
2015-10-29 5:43 ` AKASHI Takahiro
2015-10-29 13:35 ` kbuild test robot
2015-10-29 13:35 ` kbuild test robot
2015-10-29 15:09 ` Will Deacon
2015-10-29 15:09 ` Will Deacon
2015-10-30 6:00 ` libin
2015-10-30 6:00 ` libin
2015-11-02 18:26 ` Steven Rostedt
2015-11-02 18:26 ` Steven Rostedt
2015-11-02 18:28 ` Will Deacon
2015-11-02 18:28 ` Will Deacon
2015-11-02 19:34 ` Steven Rostedt
2015-11-02 19:34 ` 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=20151028115825.GB29512@arm.com \
--to=will.deacon@arm.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 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.