From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Anton Blanchard <anton@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Paul Mackerras <paulus@ozlabs.org>,
sathnaga@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] powerpc64/ftrace: Add a field in paca to disable ftrace in unsafe code paths
Date: Tue, 20 Mar 2018 00:24:27 +0530 [thread overview]
Message-ID: <1521485608.a0kau5nu5z.naveen@linux.ibm.com> (raw)
In-Reply-To: <20180319101344.72144f30@gandalf.local.home>
Steven Rostedt wrote:
> On Mon, 19 Mar 2018 14:43:00 +0530
> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
>=20
>> diff --git a/arch/powerpc/kernel/trace/ftrace_64_mprofile.S b/arch/power=
pc/kernel/trace/ftrace_64_mprofile.S
>> index 3f3e81852422..fdf702b4df25 100644
>> --- a/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
>> +++ b/arch/powerpc/kernel/trace/ftrace_64_mprofile.S
>> @@ -60,6 +60,19 @@ _GLOBAL(ftrace_caller)
>> mfxer r10
>> mfcr r11
>> =20
>> +#ifdef CONFIG_KVM
>> + lbz r3, PACA_FTRACE_DISABLED(r13)
>> + cmpdi r3, 0
>> + beq 1f
>> + mflr r3
>> + mtctr r3
>> + REST_GPR(3, r1)
>> + addi r1, r1, SWITCH_FRAME_SIZE
>> + mtlr r0
>> + bctr
>> +1:
>> +#endif
>=20
> I wonder if we should try to move the return out of the fast path (for
> cache reasons), as most of the time the above compare will be true. That
> is:
>=20
> #ifdef CONFIG_KVM
> lbz r3, PACA_FTRACE_DISABLED(r13)
> cmpdi r3, 0
> bne no_trace
> #endif
>=20
> /* rest of ftrace_caller code */
>=20
> /* after ftrace_caller... */
> bctr /* jump after _mcount site */
>=20
> #ifdef CONFIG_KVM
> no_trace:
> mflr r3
> mtctr r3
> REST_GPR(3, r1)
> addi r1, r1, SWITCH_FRAME_SIZE
> mtlr r0
> bctr
> #endif
Thanks, I'll incorporate those changes in my next version.
- Naveen
=
next prev parent reply other threads:[~2018-03-19 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 9:12 [PATCH 0/2] Disable ftrace during kvm guest entry/exit Naveen N. Rao
2018-03-19 9:13 ` [PATCH 1/2] powerpc64/ftrace: Add a field in paca to disable ftrace in unsafe code paths Naveen N. Rao
2018-03-19 10:40 ` Nicholas Piggin
2018-03-19 18:53 ` Naveen N. Rao
2018-03-19 22:34 ` Michael Ellerman
2018-03-20 0:05 ` Nicholas Piggin
2018-03-20 11:02 ` Naveen N. Rao
2018-03-19 14:13 ` Steven Rostedt
2018-03-19 18:54 ` Naveen N. Rao [this message]
2018-03-19 9:13 ` [PATCH 2/2] powerpc64/ftrace: Disable ftrace during kvm guest entry/exit Naveen N. Rao
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=1521485608.a0kau5nu5z.naveen@linux.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@ozlabs.org \
--cc=rostedt@goodmis.org \
--cc=sathnaga@linux.vnet.ibm.com \
/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).