From: Steven Rostedt <rostedt@goodmis.org>
To: Yipeng Zou <zouyipeng@huawei.com>
Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<mingo@redhat.com>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<liaochang1@huawei.com>, <chris.zjh@huawei.com>,
Joel Fernandes <joel@joelfernandes.org>
Subject: Re: [PATCH 1/2] tracing: hold caller_addr to hardirq_{enable,disable}_ip
Date: Tue, 6 Sep 2022 21:12:15 -0400 [thread overview]
Message-ID: <20220906211215.0fe6183a@gandalf.local.home> (raw)
In-Reply-To: <20220901104515.135162-2-zouyipeng@huawei.com>
On Thu, 1 Sep 2022 18:45:14 +0800
Yipeng Zou <zouyipeng@huawei.com> wrote:
> Currently, The arguments passing to lockdep_hardirqs_{on,off} was fixed
> in CALLER_ADDR0.
> The function trace_hardirqs_on_caller should have been intended to use
> caller_addr to represent the address that caller wants to be traced.
>
> For example, lockdep log in riscv showing the last {enabled,disabled} at
> __trace_hardirqs_{on,off} all the time(if called by):
> [ 57.853175] hardirqs last enabled at (2519): __trace_hardirqs_on+0xc/0x14
> [ 57.853848] hardirqs last disabled at (2520): __trace_hardirqs_off+0xc/0x14
>
> After use trace_hardirqs_xx_caller, we can get more effective information:
> [ 53.781428] hardirqs last enabled at (2595): restore_all+0xe/0x66
> [ 53.782185] hardirqs last disabled at (2596): ret_from_exception+0xa/0x10
I'm going to mark this as stable and send it in my next push to Linus.
I'll also add:
Fixes: c3bc8fd637a96 ("tracing: Centralize preemptirq tracepoints and unify their usage")
The code was copied from functions that were originally called directly,
but now that they are called indirectly, CALLER_ADDR0 is not the right
thing to use.
Thanks!
-- Steve
>
> Signed-off-by: Yipeng Zou <zouyipeng@huawei.com>
> ---
> kernel/trace/trace_preemptirq.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/trace_preemptirq.c b/kernel/trace/trace_preemptirq.c
> index 95b58bd757ce..1e130da1b742 100644
> --- a/kernel/trace/trace_preemptirq.c
> +++ b/kernel/trace/trace_preemptirq.c
> @@ -95,14 +95,14 @@ __visible void trace_hardirqs_on_caller(unsigned long caller_addr)
> }
>
> lockdep_hardirqs_on_prepare();
> - lockdep_hardirqs_on(CALLER_ADDR0);
> + lockdep_hardirqs_on(caller_addr);
> }
> EXPORT_SYMBOL(trace_hardirqs_on_caller);
> NOKPROBE_SYMBOL(trace_hardirqs_on_caller);
>
> __visible void trace_hardirqs_off_caller(unsigned long caller_addr)
> {
> - lockdep_hardirqs_off(CALLER_ADDR0);
> + lockdep_hardirqs_off(caller_addr);
>
> if (!this_cpu_read(tracing_irq_cpu)) {
> this_cpu_write(tracing_irq_cpu, 1);
next prev parent reply other threads:[~2022-09-07 1:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 10:45 [PATCH 0/2] riscv: tracing: Improve hardirq tracing message Yipeng Zou
2022-09-01 10:45 ` [PATCH 1/2] tracing: hold caller_addr to hardirq_{enable,disable}_ip Yipeng Zou
2022-09-07 1:12 ` Steven Rostedt [this message]
2022-09-01 10:45 ` [PATCH 2/2] riscv: tracing: Improve hardirq tracing message Yipeng Zou
2022-09-09 9:40 ` Yipeng Zou
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=20220906211215.0fe6183a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=aou@eecs.berkeley.edu \
--cc=chris.zjh@huawei.com \
--cc=joel@joelfernandes.org \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=zouyipeng@huawei.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
all inboxes | Powered by JetHome®