From: Mao Han <han_mao@c-sky.com>
To: linux-kernel@vger.kernel.org
Cc: Mao Han <han_mao@c-sky.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Guo Ren <guoren@kernel.org>
Subject: [PATCH v3 0/3] csky: perf callchain dwarf support
Date: Wed, 10 Apr 2019 16:16:42 +0800 [thread overview]
Message-ID: <cover.1554883878.git.han_mao@c-sky.com> (raw)
This patch set add perf DWARF unwinding support for C-SKY.
Including user registers/stack dump API, and libdw support.
CC: Peter Zijlstra <peterz@infradead.org>
CC: Ingo Molnar <mingo@redhat.com>
CC: Arnaldo Carvalho de Melo <acme@kernel.org>
CC: Alexander Shishkin <alexander.shishkin@linux.intel.com>
CC: Jiri Olsa <jolsa@redhat.com>
CC: Namhyung Kim <namhyung@kernel.org>
CC: Guo Ren <guoren@kernel.org>
Changes since v2:
- use same registers name as struct pt_regs
- code convention
Changes since v1:
- seperate the callchain support using frame pointer
Mao Han (3):
perf: use hweight64 instead of hweight_long
csky: Add support for perf registers sampling
csky: add support for libdw
arch/csky/Kconfig | 2 +
arch/csky/include/uapi/asm/perf_regs.h | 51 ++++++++++++++
arch/csky/kernel/Makefile | 1 +
arch/csky/kernel/perf_regs.c | 40 +++++++++++
tools/arch/csky/include/uapi/asm/perf_regs.h | 51 ++++++++++++++
tools/perf/Makefile.config | 6 +-
tools/perf/arch/csky/Build | 1 +
tools/perf/arch/csky/Makefile | 3 +
tools/perf/arch/csky/include/perf_regs.h | 100 +++++++++++++++++++++++++++
tools/perf/arch/csky/util/Build | 2 +
tools/perf/arch/csky/util/dwarf-regs.c | 49 +++++++++++++
tools/perf/arch/csky/util/unwind-libdw.c | 78 +++++++++++++++++++++
tools/perf/util/evsel.c | 2 +-
13 files changed, 384 insertions(+), 2 deletions(-)
create mode 100644 arch/csky/include/uapi/asm/perf_regs.h
create mode 100644 arch/csky/kernel/perf_regs.c
create mode 100644 tools/arch/csky/include/uapi/asm/perf_regs.h
create mode 100644 tools/perf/arch/csky/Build
create mode 100644 tools/perf/arch/csky/Makefile
create mode 100644 tools/perf/arch/csky/include/perf_regs.h
create mode 100644 tools/perf/arch/csky/util/Build
create mode 100644 tools/perf/arch/csky/util/dwarf-regs.c
create mode 100644 tools/perf/arch/csky/util/unwind-libdw.c
--
2.7.4
next reply other threads:[~2019-04-10 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 8:16 Mao Han [this message]
2019-04-10 8:16 ` [PATCH v3 1/3] perf: use hweight64 instead of hweight_long Mao Han
2019-04-10 13:08 ` Arnaldo Carvalho de Melo
2019-04-10 13:10 ` Arnaldo Carvalho de Melo
2019-04-10 13:28 ` Arnaldo Carvalho de Melo
2019-04-11 7:40 ` Mao Han
2019-04-12 16:40 ` [tip:perf/urgent] perf evsel: Use hweight64() instead of hweight_long(attr.sample_regs_user) tip-bot for Mao Han
2019-04-16 15:30 ` tip-bot for Mao Han
2019-04-10 8:16 ` [PATCH v3 2/3] csky: Add support for perf registers sampling Mao Han
2019-04-10 8:16 ` [PATCH v3 3/3] csky: add support for libdw Mao Han
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=cover.1554883878.git.han_mao@c-sky.com \
--to=han_mao@c-sky.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=guoren@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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).