From: Mukesh Ojha <quic_mojha@quicinc.com>
To: <linux-samsung-soc@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Cc: Trilok Soni <quic_tsoni@quicinc.com>,
"open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>
Subject: Feedback on Qualcomm's minidump (debug) solution for end user device crash
Date: Thu, 20 Jul 2023 20:32:24 +0530 [thread overview]
Message-ID: <0199db00-1b1d-0c63-58ff-03efae02cb21@quicinc.com> (raw)
Hi Samsung/MTK/Any other SOC vendors,
This is to bring to your notice that, we (Qualcomm) are working on
upstreaming our minidump solution which is to address the problem of
debugging on field device crashes where collecting entire ddr dump
would not be feasible and collecting minimal data from the ddr would
help in debug direction or even help in root causing issue.
We have recently posted v4 version here [1]
Based on comments[2], community is more worried about, if each SOC
vendor come up with their own dumping method today or in future and
whether it can have a common solution to a similar problem faced by
other SOC vendor.
We wanted to take your feedback if you also encounter a similar problem
or maintain something similar solution in downstream which can be
upstreamed. This will help us in a way to have a common solution in
upstream.
[1]
https://lore.kernel.org/lkml/10dd2ead-758a-89f0-cda4-70ae927269eb@quicinc.com/
[2]
https://lore.kernel.org/lkml/CAL_JsqLO9yey2-4FcWsaGxijiS6hGL0SH9VoMuiyei-u9=Cv=w@mail.gmail.com/
-Mukesh
next reply other threads:[~2023-07-20 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 15:02 Mukesh Ojha [this message]
2023-07-24 16:59 ` Brian Masney
2023-07-30 11:44 ` Krzysztof Kozlowski
2023-08-07 12:31 ` Mukesh Ojha
2023-08-07 15:08 ` Brian Masney
2023-08-09 7:49 ` Kukjin Kim
2023-08-09 16:17 ` Mukesh Ojha
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=0199db00-1b1d-0c63-58ff-03efae02cb21@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=quic_tsoni@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
all inboxes | Powered by JetHome®