From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
shuah@kernel.org
Subject: Re: [PATCH] selftests/ftrace: Disable multiple_kprobes test on powerpc
Date: Tue, 05 Jan 2021 16:51:50 +0530 [thread overview]
Message-ID: <1609845480.pjhqgleg8n.naveen@linux.ibm.com> (raw)
In-Reply-To: <20210105191518.fc5e602cb10fb22ef1a2303d@kernel.org>
Masami Hiramatsu wrote:
> On Tue, 5 Jan 2021 19:01:56 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
>> On Tue, 5 Jan 2021 12:27:30 +0530
>> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
>>
>> > Not all symbols are blacklisted on powerpc. Disable multiple_kprobes
>> > test until that is sorted, so that rest of ftrace and kprobe selftests
>> > can be run.
>>
>> This looks good to me, but could you try to find the functions
>> which should be blocked from kprobes?
>> (Usually, the function which are involved in the sw-breakpoint
>> handling, including locks etc.)
>
> Ah, OK.
> I wonder why CONFIG_KPROBE_EVENTS_ON_NOTRACE=n doesn't help, it
> was ignored if the arch doesn't support CONFIG_KPROBES_ON_FTRACE.
Good point, though we do support CONFIG_KPROBES_ON_FTRACE on powerpc so
the below patch is unlikely to help. However, since entry code is
unlikely to be the source of the issue due to
CONFIG_KPROBE_EVENTS_ON_NOTRACE, I will take another look to see where
the problem lies.
>
> Naveen, could you try to run this test case with following patch
> on powerpc?
>
> diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> index b911e9f6d9f5..241a55313476 100644
> --- a/kernel/trace/trace_kprobe.c
> +++ b/kernel/trace/trace_kprobe.c
> @@ -433,7 +433,7 @@ static int disable_trace_kprobe(struct trace_event_call *call,
> return 0;
> }
>
> -#if defined(CONFIG_KPROBES_ON_FTRACE) && \
> +#if defined(CONFIG_FUNCTION_TRACER) && \
> !defined(CONFIG_KPROBE_EVENTS_ON_NOTRACE)
> static bool __within_notrace_func(unsigned long addr)
> {
>
This looks like a good change regardless, so if you intend to post this
separately:
Acked-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Thanks,
Naveen
next prev parent reply other threads:[~2021-01-05 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 6:57 Naveen N. Rao
2021-01-05 10:01 ` Masami Hiramatsu
2021-01-05 10:12 ` Naveen N. Rao
2021-01-05 14:41 ` Masami Hiramatsu
2021-01-05 10:15 ` Masami Hiramatsu
2021-01-05 11:21 ` Naveen N. Rao [this message]
2021-01-05 14:33 ` Masami Hiramatsu
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=1609845480.pjhqgleg8n.naveen@linux.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.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
all inboxes | Powered by JetHome®