From: Leo Yan <leo.yan@linaro.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Wei Xu <xuwei5@hisilicon.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Daniel Thompson <daniel.thompson@linaro.org>
Cc: Leo Yan <leo.yan@linaro.org>
Subject: [PATCH RFC 0/3] coresight: enable debug module
Date: Mon, 13 Feb 2017 14:11:35 +0800 [thread overview]
Message-ID: <1486966298-16767-1-git-send-email-leo.yan@linaro.org> (raw)
This patch series is to enable coresight debug module. With debug
module we can check CPU state and PC value, etc. So this is helpful for
CPU lockup bugs, e.g. if one CPU has run into infinite loop with IRQ
disabled. The hang CPU cannot switch context and handle any interrupt,
so it cannot handle SMP call for stack dump, etc.
Furthermore, now ARMv8 introduces some runtime firmwares like ARM
trusted firmware BL31, so sometime CPU lockup may happen in the
firmware and cannot return back to kernel.
This initial patch series enable debug module and registers call back
notifier for PCSR register dumping when panic happens, so we can see
below dumping info for panic:
[ 13.751777] Coresight debug module:
[ 13.755275] CPU[0]: PSCR=0xffff000008090cbc
[ 13.759469] CPU[1]: PSCR=0xffff0000088bf9e4
[ 13.763662] CPU[2]: PSCR=0xffff000008090cc0
[ 13.767856] CPU[3]: PSCR=0xffff000008090cb8
[ 13.772049] CPU[4]: PSCR=0xffff000008090cc0
[ 13.776243] CPU[5]: PSCR=0xffff000008090cbc
[ 13.780436] CPU[6]: PSCR=0xffff000008090cc0
[ 13.784630] CPU[7]: PSCR=0xffff000008090cbc
This patch series has been verified on 96boards Hikey.
Leo Yan (3):
coresight: binding for coresight debug driver
coresight: add support for debug module
arm64: dts: register Hi6220's coresight debug module
.../devicetree/bindings/arm/coresight.txt | 9 +-
.../boot/dts/hisilicon/hikey_6220_coresight.dtsi | 73 +++++++++
drivers/hwtracing/coresight/Kconfig | 8 +
drivers/hwtracing/coresight/Makefile | 1 +
drivers/hwtracing/coresight/coresight-debug.c | 169 +++++++++++++++++++++
5 files changed, 258 insertions(+), 2 deletions(-)
create mode 100644 drivers/hwtracing/coresight/coresight-debug.c
--
2.7.4
next reply other threads:[~2017-02-13 6:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 6:11 Leo Yan [this message]
2017-02-13 6:11 ` [PATCH RFC 1/3] coresight: binding for coresight debug driver Leo Yan
2017-02-15 11:13 ` Mark Rutland
2017-02-15 20:08 ` Mathieu Poirier
2017-02-16 13:55 ` Leo Yan
2017-02-13 6:11 ` [PATCH RFC 2/3] coresight: add support for debug module Leo Yan
2017-02-15 11:43 ` Mark Rutland
2017-02-16 18:14 ` Mathieu Poirier
2017-02-15 11:44 ` Mark Rutland
2017-02-16 15:21 ` Leo Yan
2017-02-15 21:08 ` Mathieu Poirier
2017-02-16 15:26 ` Leo Yan
2017-02-13 6:11 ` [PATCH RFC 3/3] arm64: dts: register Hi6220's coresight " Leo Yan
2017-02-15 21:19 ` Mathieu Poirier
[not found] ` <CAJ9a7VjiEwUEQVvuecYS9aLbe+4-eN-waEWirdv_ctsHPaXxWw@mail.gmail.com>
2017-02-13 23:37 ` [PATCH RFC 0/3] coresight: enable " Leo Yan
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=1486966298-16767-1-git-send-email-leo.yan@linaro.org \
--to=leo.yan@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.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).