powerpc/pseries: Don't trace hcall tracing wrapper
authorNicholas Piggin <npiggin@gmail.com>
Sat, 8 May 2021 10:14:53 +0000 (20:14 +1000)
committerMichael Ellerman <mpe@ellerman.id.au>
Wed, 12 May 2021 01:07:38 +0000 (11:07 +1000)
This doesn't seem very useful to trace before the recursion check, even
if the ftrace code has any recursion checks of its own. Be on the safe
side and don't trace the hcall trace wrappers.

Reported-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Reviewed-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20210508101455.1578318-3-npiggin@gmail.com
arch/powerpc/platforms/pseries/lpar.c

index b619568a4d04ae303f7423f5af291b8996b9233c..d79d7410c32043c83d2453939f0e6144325a15da 100644 (file)
@@ -1835,7 +1835,7 @@ void hcall_tracepoint_unregfunc(void)
 static DEFINE_PER_CPU(unsigned int, hcall_trace_depth);
 
 
-void __trace_hcall_entry(unsigned long opcode, unsigned long *args)
+notrace void __trace_hcall_entry(unsigned long opcode, unsigned long *args)
 {
        unsigned long flags;
        unsigned int *depth;
@@ -1863,7 +1863,7 @@ out:
        local_irq_restore(flags);
 }
 
-void __trace_hcall_exit(long opcode, long retval, unsigned long *retbuf)
+notrace void __trace_hcall_exit(long opcode, long retval, unsigned long *retbuf)
 {
        unsigned long flags;
        unsigned int *depth;