From: Max Filippov <jcmvbkbc@gmail.com>
To: linux-xtensa@linux-xtensa.org, linux-kernel@vger.kernel.org
Cc: Chris Zankel <chris@zankel.net>, Marc Gauthier <marc@cadence.com>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [PATCH 0/8] Support hardware perf counters on xtensa
Date: Mon, 6 Jul 2015 16:32:41 +0300 [thread overview]
Message-ID: <1436189569-28802-1-git-send-email-jcmvbkbc@gmail.com> (raw)
Hello,
this series adds support for hardware performance counters in counting and
sampling modes as well as for page fault counting. It reorganizes stack
stracing code to share it between old oprofile and new perf interfaces,
and improves kernel stack traces both for builtin debug functions and for
gdb.
Max Filippov (8):
xtensa: clean up Kconfig dependencies for custom cores
xtensa: keep exception/interrupt stack continuous
xtensa: move oprofile stack tracing to stacktrace.c
xtensa: select PERF_USE_VMALLOC for cache-aliasing configurations
xtensa: add profiling IRQ type to xtensa_irq_map
xtensa: count software page fault perf events
xtensa: implement counting and sampling perf events
perf tools: xtensa: add DWARF register names
arch/xtensa/Kconfig | 22 +-
arch/xtensa/include/asm/stacktrace.h | 8 +
arch/xtensa/kernel/Makefile | 1 +
arch/xtensa/kernel/entry.S | 60 +++--
arch/xtensa/kernel/irq.c | 6 +
arch/xtensa/kernel/perf_event.c | 450 +++++++++++++++++++++++++++++++
arch/xtensa/kernel/stacktrace.c | 167 +++++++++++-
arch/xtensa/mm/fault.c | 7 +
arch/xtensa/oprofile/backtrace.c | 158 +----------
tools/perf/arch/xtensa/Build | 1 +
tools/perf/arch/xtensa/Makefile | 3 +
tools/perf/arch/xtensa/util/Build | 1 +
tools/perf/arch/xtensa/util/dwarf-regs.c | 25 ++
13 files changed, 725 insertions(+), 184 deletions(-)
create mode 100644 arch/xtensa/kernel/perf_event.c
create mode 100644 tools/perf/arch/xtensa/Build
create mode 100644 tools/perf/arch/xtensa/Makefile
create mode 100644 tools/perf/arch/xtensa/util/Build
create mode 100644 tools/perf/arch/xtensa/util/dwarf-regs.c
--
1.8.1.4
next reply other threads:[~2015-07-06 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 13:32 Max Filippov [this message]
2015-07-06 13:32 ` [PATCH 1/8] xtensa: clean up Kconfig dependencies for custom cores Max Filippov
2015-07-07 9:18 ` Paul Bolle
2015-07-06 13:32 ` [PATCH 2/8] xtensa: keep exception/interrupt stack continuous Max Filippov
2015-07-07 18:47 ` Chris Zankel
2015-07-07 19:46 ` Max Filippov
2015-07-07 19:47 ` Max Filippov
2015-07-06 13:32 ` [PATCH 3/8] xtensa: move oprofile stack tracing to stacktrace.c Max Filippov
2015-07-06 13:32 ` [PATCH 4/8] xtensa: select PERF_USE_VMALLOC for cache-aliasing configurations Max Filippov
2015-07-06 13:32 ` [PATCH 5/8] xtensa: add profiling IRQ type to xtensa_irq_map Max Filippov
2015-07-06 13:32 ` [PATCH 6/8] xtensa: count software page fault perf events Max Filippov
2015-07-06 13:32 ` [PATCH 7/8] xtensa: implement counting and sampling " Max Filippov
2015-07-06 13:41 ` Peter Zijlstra
2015-07-06 13:49 ` Max Filippov
2015-07-06 13:47 ` Peter Zijlstra
2015-07-06 13:56 ` Max Filippov
2015-07-06 14:05 ` Peter Zijlstra
2015-07-06 14:22 ` Max Filippov
2015-07-07 3:56 ` Chris Zankel
2015-07-06 13:32 ` [PATCH 8/8] perf tools: xtensa: add DWARF register names Max Filippov
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=1436189569-28802-1-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=marc@cadence.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