From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-riscv@lists.infradead.org, aou@eecs.berkeley.edu,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH 0/3] riscv: cover to ARCH_STACKWALK
Date: Thu, 17 Dec 2020 10:34:58 +0800 [thread overview]
Message-ID: <e103e594-d7f5-7a43-6d5d-da538e44b795@huawei.com> (raw)
In-Reply-To: <mhng-54bff36c-7c0d-4448-8859-d8d05cbd8b0d@palmerdabbelt-glaptop1>
On 2020/11/21 11:01, Palmer Dabbelt wrote:
> On Thu, 12 Nov 2020 22:42:20 PST (-0800), wangkefeng.wang@huawei.com
> wrote:
>> Use the newer common infrastructure and simpler arch_stack_walk()
>> interface
>> for stack walk.
>>
>> Kefeng Wang (3):
>> riscv: Cleanup stacktrace
>> riscv: Make stack walk callback consistent with generic code
>> riscv: Enable ARCH_STACKWALK
>>
>> arch/riscv/Kconfig | 1 +
>> arch/riscv/include/asm/stacktrace.h | 17 ++++++++
>> arch/riscv/kernel/perf_callchain.c | 10 +----
>> arch/riscv/kernel/stacktrace.c | 62 +++++++----------------------
>> 4 files changed, 34 insertions(+), 56 deletions(-)
>> create mode 100644 arch/riscv/include/asm/stacktrace.h
>
> Thanks, these are on for-next.
hi Palmer, I found a extra code about deleting "__INIT", is there a
mistaken when merged into for- next?
see link
https://kernel.googlesource.com/pub/scm/linux/kernel/git/riscv/linux/+/5cb0080f1bfdccb56d5c225d1cd648cdb33fa9bb%5E%21/#F1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2020-12-17 2:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 6:42 [PATCH 0/3] riscv: cover to ARCH_STACKWALK Kefeng Wang
2020-11-13 6:42 ` [PATCH 1/3] riscv: Cleanup stacktrace Kefeng Wang
2020-11-13 6:42 ` [PATCH 2/3] riscv: Make stack walk callback consistent with generic code Kefeng Wang
2020-11-13 6:42 ` [PATCH 3/3] riscv: Enable ARCH_STACKWALK Kefeng Wang
2020-11-21 3:01 ` [PATCH 0/3] riscv: cover to ARCH_STACKWALK Palmer Dabbelt
2020-11-24 11:20 ` [PATCH 1/2] riscv: Add dump stack in show_regs Kefeng Wang
2020-11-24 11:20 ` [PATCH 2/2] riscv: Fix __show_regs printing formats Kefeng Wang
2020-11-25 22:58 ` Atish Patra
2020-11-26 1:10 ` Kefeng Wang
2020-11-26 10:02 ` John Ogness
2020-11-26 11:55 ` John Ogness
2020-11-26 12:49 ` Kefeng Wang
2020-11-26 13:33 ` [PATCH v2] riscv: Using printk directly in __show_regs Kefeng Wang
2020-12-11 1:43 ` Palmer Dabbelt
2020-12-11 8:48 ` John Ogness
2020-12-14 11:49 ` Kefeng Wang
2020-11-25 23:04 ` [PATCH 1/2] riscv: Add dump stack in show_regs Atish Patra
2020-12-14 11:52 ` Kefeng Wang
2021-01-09 22:24 ` Palmer Dabbelt
2021-01-11 3:23 ` Kefeng Wang
2020-12-17 2:34 ` Kefeng Wang [this message]
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=e103e594-d7f5-7a43-6d5d-da538e44b795@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@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