From: Christoph Hellwig <hch@infradead.org>
To: Mao Han <han_mao@c-sky.com>
Cc: linux-kernel@vger.kernel.org, Palmer Dabbelt <palmer@sifive.com>
Subject: Re: [PATCH 1/3] riscv: Add perf callchain support
Date: Thu, 11 Apr 2019 07:24:32 -0700 [thread overview]
Message-ID: <20190411142432.GB8343@infradead.org> (raw)
In-Reply-To: <195185ea63240ed396026505d96d1f6449963482.1554961908.git.han_mao@c-sky.com>
> --- /dev/null
> +++ b/arch/riscv/kernel/perf_callchain.c
> @@ -0,0 +1,122 @@
> +// SPDX-License-Identifier: GPL-2.0
> +// Copyright (C) 2019 Hangzhou C-SKY Microsystems co.,ltd.
Please use normal /* */ Style comment for everything but the SPDX
tags.
> +static int unwind_frame_kernel(struct stackframe *frame)
> +{
> + int graph = 0;
> +
> + /* 0x3 means misalignment */
> + if (!kstack_end((void *)frame->fp) &&
> + !((unsigned long)frame->fp & 0x3) &&
> + ((unsigned long)frame->fp >= TASK_SIZE)) {
> + frame->ra = ((struct stackframe *)frame->fp - 1)->ra;
> + frame->fp = ((struct stackframe *)frame->fp - 1)->fp;
> + /* make sure CONFIG_FUNCTION_GRAPH_TRACER is turned on */
> + if (__kernel_text_address(frame->ra))
> + frame->ra = ftrace_graph_ret_addr(NULL, &graph,
> + frame->ra, NULL);
> + return 0;
> + } else {
> + return -EPERM;
> + }
Please do early exists for all the error conditions. Also no casts
are needed for using ->fp as a scalar value, and we should probably
just do a struct copy instead of copying both values individually.
The function should look something like:
static int unwind_frame_kernel(struct stackframe *frame)
{
if (!kstack_end((void *)frame->fp))
return -EPERM;
if ((frame->fp & 0x3 || frame->fp >= TASK_SIZE)
return -EPERM;
*frame = *((struct stackframe *)frame->fp - 1);
if (__kernel_text_address(frame->ra)) {
int graph = 0;
frame->ra = ftrace_graph_ret_addr(NULL, &graph, frame->ra,
NULL);
}
return 0;
}
> +static void notrace walk_stackframe(struct stackframe *fr,
> + struct perf_callchain_entry_ctx *entry)
> +{
> + while (1) {
> + int ret;
> +
> + perf_callchain_store(entry, fr->ra);
> +
> + ret = unwind_frame_kernel(fr);
> + if (ret < 0)
> + break;
> + }
> +}
Why not:
do {
perf_callchain_store(entry, fr->ra);
} while (unwind_frame_kernel(fr) >= 0);
> +/*
> + * Get the return address for a single stackframe and return a pointer to the
> + * next frame tail.
> + */
> +static unsigned long user_backtrace(struct perf_callchain_entry_ctx *entry,
> + unsigned long fp, unsigned long reg_ra)
> +{
> + struct stackframe buftail;
> + unsigned long ra = 0;
> + unsigned long *user_frame_tail = (unsigned long *)(fp - sizeof(struct stackframe));
Overly long line.
> + fp = user_backtrace(entry, fp, regs->ra);
> + while ((entry->nr < entry->max_stack) &&
> + fp && !((unsigned long)fp & 0x3))
> + fp = user_backtrace(entry, fp, 0);
Please don't indent the condition continuation and the loop body
by the same amount.
next prev parent reply other threads:[~2019-04-11 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 7:53 [PATCH 0/3] riscv: Add perf callchain support Mao Han
2019-04-11 7:53 ` [PATCH 1/3] " Mao Han
2019-04-11 14:24 ` Christoph Hellwig [this message]
2019-04-25 21:11 ` Palmer Dabbelt
2019-04-29 8:39 ` Mao Han
2019-04-11 7:53 ` [PATCH 2/3] riscv: Add support for perf registers sampling Mao Han
2019-04-25 21:11 ` Palmer Dabbelt
2019-04-29 8:42 ` Mao Han
2019-04-11 7:53 ` [PATCH 3/3] riscv: Add support for libdw Mao Han
2019-04-25 21:11 ` Palmer Dabbelt
2019-04-29 8:45 ` Mao Han
2019-04-11 14:14 ` [PATCH 0/3] riscv: Add perf callchain support Christoph Hellwig
2019-04-12 9:38 ` [PATCH 2/3] riscv: Add support for perf registers sampling Mao Han
2019-04-13 8:01 ` Christoph Hellwig
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=20190411142432.GB8343@infradead.org \
--to=hch@infradead.org \
--cc=han_mao@c-sky.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@sifive.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).