From: Gurbir Arora <gurbaror@codeaurora.org>
To: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: bjorn.andersson@linaro.org, mathieu.poirier@linaro.org,
tsoni@codeaurora.org, psodagud@codeaurora.org,
sidgup@codeaurora.org, rishabhb@codeaurora.org,
Gurbir Arora <gurbaror@codeaurora.org>
Subject: [PATCH 0/3] Introduce mini-dump support for remoteproc.
Date: Fri, 7 Aug 2020 16:31:58 -0700 [thread overview]
Message-ID: <1596843121-82576-1-git-send-email-gurbaror@codeaurora.org> (raw)
Sometimes firmware sizes can be in ten's of MB's and reading
all the memory during coredump can consume lot of time and
memory.
Introducing support for mini-dumps. Mini-dump contains smallest
amount of useful information, that could help to debug subsystem
crashes.
During bootup memory is allocated in SMEM (Shared memory)
in the form of a table that contains the physical
addresses and sizes of the regions that are supposed to be
collected during coredump. This memory is shared amongst all
processors in a Qualcomm platform, so all remoteprocs
fill in their entry in the global table once they are out
of reset.
This patch series adds support for parsing the global minidump
table and uses the current coredump frameork to expose this memory
to userspace during remoteproc's recovery.
This patch series also integrates the patch:
https://patchwork.kernel.org/patch/11695541/ sent by Siddharth.
Gurbir Arora (2):
remoteproc: core: Add coredump to remoteproc ops
remoteproc: qcom: Add capability to collect minidumps
Rishabh Bhatnagar (1):
remoteproc: qcom: Add minidump id for sm8150 modem remoteproc
drivers/remoteproc/qcom_minidump.h | 64 +++++++++
drivers/remoteproc/qcom_q6v5_pas.c | 21 ++-
drivers/remoteproc/remoteproc_core.c | 7 +-
drivers/remoteproc/remoteproc_coredump.c | 211 +++++++++++++++++++++++++++-
drivers/remoteproc/remoteproc_elf_helpers.h | 27 ++++
drivers/remoteproc/remoteproc_internal.h | 2 +
include/linux/remoteproc.h | 3 +
7 files changed, 331 insertions(+), 4 deletions(-)
create mode 100644 drivers/remoteproc/qcom_minidump.h
--
1.9.1
next reply other threads:[~2020-08-07 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 23:31 Gurbir Arora [this message]
2020-08-07 23:31 ` [PATCH 1/3] remoteproc: core: Add coredump to remoteproc ops Gurbir Arora
2020-08-10 22:54 ` Mathieu Poirier
2020-08-07 23:32 ` [PATCH 2/3] remoteproc: qcom: Add capability to collect minidumps Gurbir Arora
2020-08-08 1:41 ` kernel test robot
2020-08-08 2:21 ` kernel test robot
2020-08-07 23:32 ` [PATCH 3/3] remoteproc: qcom: Add minidump id for sm8150 modem remoteproc Gurbir Arora
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=1596843121-82576-1-git-send-email-gurbaror@codeaurora.org \
--to=gurbaror@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=psodagud@codeaurora.org \
--cc=rishabhb@codeaurora.org \
--cc=sidgup@codeaurora.org \
--cc=tsoni@codeaurora.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).