From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Enable ramoops on Tegra210 and newer
Date: Thu, 29 May 2025 10:52:59 +0200 [thread overview]
Message-ID: <6abdc70c-0def-4cf1-b1f4-ea9bdde4fcb5@kernel.org> (raw)
In-Reply-To: <CALHNRZ--ZUxqrXHEnizXC8ddHC5LFA10oH+CgQmOcTt+cJ1CWw@mail.gmail.com>
On 28/05/2025 19:35, Aaron Kling wrote:
>>>>
>>>> Friendly reminder to the Tegra maintainers about this question.
>>>>
>>> In lieu of a response from the Tegra subsystem maintainers, I can only
>>> hazard an assumption, Krzysztof. I presume the pstore carveout is
>>> bootloader controlled because various stages of the boot stack can
>>> dynamically allocate memory, and this became bootloader controlled to
>>> prevent any of those from overwriting pstore. I worry about hardcoding
>>> an address in the kernel dt, then finding out later that there's an
>>> in-use configuration that overwrites or corrupts that section of ram
>>> during boot. What are your thoughts on this? And is there any way for
>>> this patch to proceed?
>>
>> I haven't been able to find anything out about this yet. Generally it's
>> difficult to get the bootloaders updated for these devices. Tegra194 and
>> Tegra234 may be new enough to make an update eventually go into a
>> release, but for Tegra186 and older, I honestly wouldn't hold my
>> breath.
>>
>> Thierry
>
> Krzysztof, based on this response, is there any way or form that the
> Tegra186 part of this could be submitted? I can drop the newer
> platforms from this patch if Thierry can get a response to his other
> reply about how the bootloader could conform.
>
I don't NAK it. Eventually it is up to platform maintainer if they
accept known DTC warnings.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-29 8:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 21:12 [PATCH] arm64: tegra: Enable ramoops on Tegra210 and newer Aaron Kling via B4 Relay
2025-04-07 12:47 ` Rob Herring (Arm)
2025-04-07 12:59 ` Krzysztof Kozlowski
2025-04-07 16:00 ` Aaron Kling
2025-04-08 6:07 ` Krzysztof Kozlowski
2025-04-08 7:35 ` Aaron Kling
2025-04-08 8:17 ` Krzysztof Kozlowski
2025-04-08 8:49 ` Aaron Kling
2025-04-21 1:45 ` Aaron Kling
2025-04-29 1:21 ` Aaron Kling
2025-05-08 21:27 ` Thierry Reding
2025-05-28 17:35 ` Aaron Kling
2025-05-29 8:52 ` Krzysztof Kozlowski [this message]
2025-06-30 18:48 ` Aaron Kling
2025-07-03 7:24 ` Thierry Reding
2025-07-14 6:01 ` Aaron Kling
2025-07-31 21:24 ` Aaron Kling
2025-08-01 9:49 ` Thierry Reding
2025-05-08 21:33 ` Thierry Reding
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=6abdc70c-0def-4cf1-b1f4-ea9bdde4fcb5@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=jonathanh@nvidia.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony.luck@intel.com \
--cc=webgeek1234@gmail.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;
as well as URLs for NNTP newsgroup(s).