linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Siddharth Gupta <sidgup@codeaurora.org>
To: agross@kernel.org, bjorn.andersson@linaro.org, ohad@wizery.com
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, tsoni@codeaurora.org,
	psodagud@codeaurora.org, rishabhb@codeaurora.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 0/3] Introduce mini-dump support for remoteproc
Date: Thu, 17 Sep 2020 11:20:08 -0700	[thread overview]
Message-ID: <5a8002bd-2eaa-5acd-d7ad-b651dd5e4fbb@codeaurora.org> (raw)
In-Reply-To: <01010174796142bd-a595147b-833a-48fe-b692-f8b6fe466146-000000@us-west-2.amazonses.com>

Gentle remind to review this patch series.

Thanks,
Sid

On 9/10/2020 11:57 AM, Siddharth Gupta wrote:
> 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.
>
> Changelog:
> v3 -> v4:
> - Made adsp_priv_cleanup a static function.
>
> v2 -> v3:
> - Refactored code to remove dependency on Qualcomm configs.
> - Renamed do_rproc_minidump to rproc_minidump and marked as exported
>    symbol.
>
> v1 -> v2:
> - 3 kernel test robot warnings have been resolved.
> - Introduced priv_cleanup op in order to making the cleaning of
>    private elements used by the remoteproc more readable.
> - Removed rproc_cleanup_priv as it is no longer needed.
> - Switched to if/else format for rproc_alloc in order to keep
>    the static const decalaration of adsp_minidump_ops.
>
> Siddharth Gupta (3):
>    remoteproc: core: Add ops to enable custom coredump functionality
>    remoteproc: qcom: Add capability to collect minidumps
>    remoteproc: qcom: Add minidump id for sm8150 modem remoteproc
>
>   drivers/remoteproc/qcom_minidump.h          |  64 +++++++++++++
>   drivers/remoteproc/qcom_q6v5_pas.c          | 107 ++++++++++++++++++++-
>   drivers/remoteproc/remoteproc_core.c        |   6 +-
>   drivers/remoteproc/remoteproc_coredump.c    | 138 ++++++++++++++++++++++++++++
>   drivers/remoteproc/remoteproc_elf_helpers.h |  27 ++++++
>   include/linux/remoteproc.h                  |   5 +
>   6 files changed, 344 insertions(+), 3 deletions(-)
>   create mode 100644 drivers/remoteproc/qcom_minidump.h
>

      reply	other threads:[~2020-09-17 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 18:57 [PATCH v4 0/3] Introduce mini-dump support for remoteproc Siddharth Gupta
2020-09-17 18:20 ` Siddharth Gupta [this message]

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=5a8002bd-2eaa-5acd-d7ad-b651dd5e4fbb@codeaurora.org \
    --to=sidgup@codeaurora.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=psodagud@codeaurora.org \
    --cc=rishabhb@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).