From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Yogesh Lal <quic_ylal@quicinc.com>
Cc: quic_sibis@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: qcom: Add fallback mechanism for full coredump collection
Date: Fri, 22 Apr 2022 10:22:24 -0500 [thread overview]
Message-ID: <YmLIMG62vPv4qtVe@builder.lan> (raw)
In-Reply-To: <1649269662-20338-1-git-send-email-quic_ylal@quicinc.com>
On Wed 06 Apr 13:27 CDT 2022, Yogesh Lal wrote:
> In case remoteproc's firmware missing minidump support, during crash
> scenario coredump does not collected. This change adds a fallback
> mechanism for full coredump collection in the event of a crash.
>
> Signed-off-by: Yogesh Lal <quic_ylal@quicinc.com>
> ---
> drivers/remoteproc/qcom_common.c | 11 ++++++++---
> drivers/remoteproc/qcom_q6v5_pas.c | 1 +
> 2 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/remoteproc/qcom_common.c b/drivers/remoteproc/qcom_common.c
> index 4b91e3c..68bd0bc 100644
> --- a/drivers/remoteproc/qcom_common.c
> +++ b/drivers/remoteproc/qcom_common.c
> @@ -162,13 +162,18 @@ void qcom_minidump(struct rproc *rproc, unsigned int minidump_id)
> * is initialized in memory and encryption status is set.
> */
> if (subsystem->regions_baseptr == 0 ||
> - le32_to_cpu(subsystem->status) != 1 ||
> - le32_to_cpu(subsystem->enabled) != MD_SS_ENABLED ||
> - le32_to_cpu(subsystem->encryption_status) != MD_SS_ENCR_DONE) {
> + le32_to_cpu(subsystem->status) != 1 ||
> + le32_to_cpu(subsystem->enabled) != MD_SS_ENABLED) {
> + return rproc_coredump(rproc);
> + }
> +
> + if (le32_to_cpu(subsystem->encryption_status) != MD_SS_ENCR_DONE) {
> dev_err(&rproc->dev, "Minidump not ready, skipping\n");
> return;
> }
>
> + rproc_coredump_cleanup(rproc);
The patch looks good, but could you please explain in the commit message
why this needs to be added? If the thing described in the message
happens this code path wouldn't be taken.
Should it be a separate patch, or is it needed because of the fallback
etc?
Thanks,
Bjorn
> +
> ret = qcom_add_minidump_segments(rproc, subsystem);
> if (ret) {
> dev_err(&rproc->dev, "Failed with error: %d while adding minidump entries\n", ret);
> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
> index 1ae47cc..40bf747 100644
> --- a/drivers/remoteproc/qcom_q6v5_pas.c
> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
> @@ -293,6 +293,7 @@ static const struct rproc_ops adsp_minidump_ops = {
> .start = adsp_start,
> .stop = adsp_stop,
> .da_to_va = adsp_da_to_va,
> + .parse_fw = qcom_register_dump_segments,
> .load = adsp_load,
> .panic = adsp_panic,
> .coredump = adsp_minidump,
> --
> 2.7.4
>
next prev parent reply other threads:[~2022-04-22 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 18:27 [PATCH] remoteproc: qcom: Add fallback mechanism for full coredump collection Yogesh Lal
2022-04-22 15:22 ` Bjorn Andersson [this message]
2022-04-26 10:15 ` Yogesh Lal
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=YmLIMG62vPv4qtVe@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=quic_sibis@quicinc.com \
--cc=quic_ylal@quicinc.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