From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <bjorn@kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<namhyung@kernel.org>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <jolsa@kernel.org>,
<irogers@google.com>, <adrian.hunter@intel.com>,
<kan.liang@linux.intel.com>, <dev.mbstr@gmail.com>,
<samuel.holland@sifive.com>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>
Cc: <ruanjinjie@huawei.com>
Subject: [PATCH v3 0/2] riscv: stacktrace: Add USER_STACKTRACE support
Date: Mon, 8 Jul 2024 11:28:45 +0800 [thread overview]
Message-ID: <20240708032847.2998158-1-ruanjinjie@huawei.com> (raw)
Add RISC-V USER_STACKTRACE support, and fix the fp alignment bug
in perf_callchain_user() by the way as Björn pointed out.
Changes in v3:
- Fix the fp alignment bug in perf_callchain_user().
- Remove the LTP message as Björn suggested.
- Add the userstack trace test info.
Jinjie Ruan (2):
riscv: Fix fp alignment bug in perf_callchain_user()
riscv: stacktrace: Add USER_STACKTRACE support
arch/riscv/Kconfig | 1 +
arch/riscv/kernel/perf_callchain.c | 46 ++----------------------------
arch/riscv/kernel/stacktrace.c | 43 ++++++++++++++++++++++++++++
3 files changed, 47 insertions(+), 43 deletions(-)
--
2.34.1
next reply other threads:[~2024-07-08 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 3:28 Jinjie Ruan [this message]
2024-07-08 3:28 ` [PATCH v3 1/2] riscv: Fix fp alignment bug in perf_callchain_user() Jinjie Ruan
2024-07-08 3:28 ` [PATCH v3 2/2] riscv: stacktrace: Add USER_STACKTRACE support Jinjie Ruan
2024-07-23 1:40 ` Jinjie Ruan
2024-09-17 13:00 ` [PATCH v3 0/2] " patchwork-bot+linux-riscv
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=20240708032847.2998158-1-ruanjinjie@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=dev.mbstr@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=samuel.holland@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).