From: Konrad Dybcio <konradybcio@kernel.org>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>,
andersson@kernel.org, jacek.lawrynowicz@linux.intel.com,
quic_carlv@quicinc.com
Cc: ogabbay@kernel.org, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] accel/qaic: Add crashdump to Sahara
Date: Thu, 19 Sep 2024 01:41:01 +0200 [thread overview]
Message-ID: <630b2044-eaec-4a8a-bd29-d20751d33e2f@kernel.org> (raw)
In-Reply-To: <20240918155254.3186031-1-quic_jhugo@quicinc.com>
On 18.09.2024 5:52 PM, Jeffrey Hugo wrote:
> The Sahara protocol has a crashdump functionality. In the hello
> exchange, the device can advertise it has a memory dump available for
> the host to collect. Instead of the device making requests of the host,
> the host requests data from the device which can be later analyzed.
>
> Implement this functionality and utilize the devcoredump framework for
> handing the dump over to userspace.
>
> Similar to how firmware loading in Sahara involves multiple files,
> crashdump can consist of multiple files for different parts of the dump.
> Structure these into a single buffer that userspace can parse and
> extract the original files from.
>
> Reviewed-by: Carl Vanderlip <quic_carlv@quicinc.com>
> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> ---
I gave this a brief read, but.. aren't you dumping however much DRAM the
AIC100 has (and then some SRAM) onto the host machine without the user
asking for it (i.e. immediately after the AIC crashes)?
Konrad
next prev parent reply other threads:[~2024-09-18 23:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 15:52 [PATCH] accel/qaic: Add crashdump to Sahara Jeffrey Hugo
2024-09-18 23:41 ` Konrad Dybcio [this message]
2024-09-19 15:00 ` Jeffrey Hugo
2024-09-19 15:36 ` Konrad Dybcio
2024-10-14 21:52 ` Bjorn Andersson
2024-10-15 18:34 ` Jeffrey Hugo
2024-10-15 19:04 ` Bjorn Andersson
2024-10-21 17:00 ` Jeffrey Hugo
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=630b2044-eaec-4a8a-bd29-d20751d33e2f@kernel.org \
--to=konradybcio@kernel.org \
--cc=andersson@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@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