From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Xuefeng Li <lixuefeng@loongson.cn>,
Juxin Gao <gaojuxin@loongson.cn>,
David Daney <david.daney@cavium.com>,
Ralf Baechle <ralf@linux-mips.org>,
Archer Yan <ayan@wavecomp.com>
Subject: Re: [PATCH v2 1/3] MIPS: kernel: Support extracting off-line stack traces from user-space with perf
Date: Thu, 4 Feb 2021 21:59:45 +0100 [thread overview]
Message-ID: <20210204205945.GC19460@alpha.franken.de> (raw)
In-Reply-To: <1612409724-3516-2-git-send-email-yangtiezhu@loongson.cn>
On Thu, Feb 04, 2021 at 11:35:22AM +0800, Tiezhu Yang wrote:
> Add perf_event_mips_regs/perf_reg_value/perf_reg_validate to support
> features HAVE_PERF_REGS/HAVE_PERF_USER_STACK_DUMP in kernel.
>
> [ayan@wavecomp.com: Repick this patch for unwinding userstack backtrace
> by perf and libunwind on MIPS based CPU.]
>
> [ralf@linux-mips.org: Add perf_get_regs_user() which is required after
> 'commit 88a7c26af8da ("perf: Move task_pt_regs sampling into arch code")'.]
>
> [yangtiezhu@loongson.cn: Fix build error about perf_get_regs_user() after
> commit 76a4efa80900 ("perf/arch: Remove perf_sample_data::regs_user_copy"),
> and also separate the original patches into two parts (MIPS kernel and perf
> tools) to merge easily.]
>
> The original patches:
> https://lore.kernel.org/patchwork/patch/1126521/
> https://lore.kernel.org/patchwork/patch/1126520/
>
> Signed-off-by: David Daney <david.daney@cavium.com>
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
> Signed-off-by: Archer Yan <ayan@wavecomp.com>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
>
> v2: add R26 and R27 to the enum perf_event_mips_regs
>
> arch/mips/Kconfig | 2 +
> arch/mips/include/uapi/asm/perf_regs.h | 40 ++++++++++++++++++++
> arch/mips/kernel/Makefile | 2 +-
> arch/mips/kernel/perf_regs.c | 68 ++++++++++++++++++++++++++++++++++
> 4 files changed, 111 insertions(+), 1 deletion(-)
> create mode 100644 arch/mips/include/uapi/asm/perf_regs.h
> create mode 100644 arch/mips/kernel/perf_regs.c
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2021-02-04 21:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 3:35 [PATCH v2 0/3] Add some perf support for mips Tiezhu Yang
2021-02-04 3:35 ` [PATCH v2 1/3] MIPS: kernel: Support extracting off-line stack traces from user-space with perf Tiezhu Yang
2021-02-04 20:59 ` Thomas Bogendoerfer [this message]
2021-02-04 3:35 ` [PATCH v2 2/3] perf tools: Support mips unwinding and dwarf-regs Tiezhu Yang
2021-02-04 3:35 ` [PATCH v2 3/3] perf tools: Generate mips syscalls_n64.c syscall table Tiezhu Yang
2021-02-22 6:43 ` [PATCH v2 0/3] Add some perf support for mips Tiezhu Yang
2021-02-24 13:16 ` Arnaldo Carvalho de Melo
2021-02-25 12:49 ` Arnaldo Carvalho de Melo
2021-02-25 13:10 ` Arnaldo Carvalho de Melo
2021-02-25 13:12 ` Arnaldo Carvalho de Melo
2021-02-26 1:11 ` Tiezhu Yang
2021-02-26 23:49 ` Arnaldo Carvalho de Melo
2021-03-01 17:50 ` Arnaldo Carvalho de Melo
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=20210204205945.GC19460@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ayan@wavecomp.com \
--cc=david.daney@cavium.com \
--cc=gaojuxin@loongson.cn \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ralf@linux-mips.org \
--cc=yangtiezhu@loongson.cn \
/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).