From: Borislav Petkov <bp@alien8.de>
To: "Santino Wang (王俊傑)" <Santino.Wang@mediatek.com>
Cc: "jonathan.cameron@oss.qualcomm.com"
<jonathan.cameron@oss.qualcomm.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"Sidney Chang (張履平)" <Sidney.Chang@mediatek.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Fred-WY Chen (陳威宇)" <Fred-WY.Chen@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Light Chen (陳昱光)" <Light.Chen@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"Arnab Layek" <Arnab.Layek@mediatek.com>
Subject: Re: [RFC PATCH 00/11] soc: mediatek: add a DRAM ECC error handling driver
Date: Wed, 4 Nov 2026 20:53:21 -0800 [thread overview]
Message-ID: <20261105045321.GAauwLwdk2PSruRAcw@fat_crate.local> (raw)
In-Reply-To: <78ce4a6ef441cb9836466e9ae5e72ffe21a88242.camel@mediatek.com>
On Thu, Nov 05, 2026 at 04:19:27AM +0000, Santino Wang (王俊傑) wrote:
> Which existing interfaces would you recommend for obtaining retirement
> status from each memory owner? With that information available, can items
> 5–7 be maintained in userspace, or would they require support from an MTK
> driver?
mm/memory-failure.c
Look how the others use it.
What you write above sounds like you need an EDAC driver which collects and
reports errors. Look at examples in drivers/edac/ and there's some
documentation in Documentation/edac/. Perhaps ask AI too.
If the stuff you need is not there, you can extend the existing interfaces by
justifying the extensions properly.
But what you have - a completely separate RAS implementation, homegrown
somewhere else in the kernel doesn't fly. I'm actually wondering how you even
managed to do this driver without *finding* all the RAS/EDAC glue we have in
the kernel. Googling for it would've told you that there's something...
HTH.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2026-11-05 4:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 9:23 santino.wang
2026-11-02 9:23 ` [RFC PATCH 01/11] soc: mediatek: dram-ecc: add the DRAM ECC driver skeleton santino.wang
2026-11-02 13:41 ` Krzysztof Kozlowski
2026-11-02 9:23 ` [RFC PATCH 02/11] soc: mediatek: dram-ecc: add the SMC interface to the secure firmware santino.wang
2026-11-02 9:23 ` [RFC PATCH 03/11] soc: mediatek: dram-ecc: add tracepoints santino.wang
2026-11-02 19:57 ` Jonathan Cameron
2026-11-04 2:44 ` Santino Wang (王俊傑)
2026-11-05 4:01 ` Jonathan Cameron
2026-11-02 9:23 ` [RFC PATCH 04/11] soc: mediatek: dram-ecc: handle GHES vendor records from the firmware santino.wang
2026-11-02 9:23 ` [RFC PATCH 05/11] soc: mediatek: dram-ecc: add error counters and the address lists santino.wang
2026-11-02 13:42 ` Krzysztof Kozlowski
2026-11-02 9:23 ` [RFC PATCH 06/11] soc: mediatek: dram-ecc: keep error counters across boots santino.wang
2026-11-02 9:23 ` [RFC PATCH 07/11] soc: mediatek: dram-ecc: add containment policy and storm protection santino.wang
2026-11-02 9:23 ` [RFC PATCH 08/11] soc: mediatek: dram-ecc: add the corrected error leaky bucket santino.wang
2026-11-02 20:19 ` Jonathan Cameron
2026-11-02 9:23 ` [RFC PATCH 09/11] soc: mediatek: dram-ecc: add a generic netlink event interface santino.wang
2026-11-02 20:20 ` Jonathan Cameron
2026-11-02 9:23 ` [RFC PATCH 10/11] soc: mediatek: dram-ecc: report an uncorrectable error of the previous boot santino.wang
2026-11-02 13:44 ` Krzysztof Kozlowski
2026-11-02 9:23 ` [RFC PATCH 11/11] Documentation: ABI: add the sysfs attributes of the MediaTek DRAM ECC driver santino.wang
2026-11-02 20:36 ` [RFC PATCH 00/11] soc: mediatek: add a DRAM ECC error handling driver Jonathan Cameron
2026-11-02 20:44 ` Jonathan Cameron
2026-11-05 4:19 ` Santino Wang (王俊傑)
2026-11-05 4:53 ` Borislav Petkov [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=20261105045321.GAauwLwdk2PSruRAcw@fat_crate.local \
--to=bp@alien8.de \
--cc=Arnab.Layek@mediatek.com \
--cc=Fred-WY.Chen@mediatek.com \
--cc=Light.Chen@mediatek.com \
--cc=Santino.Wang@mediatek.com \
--cc=Sidney.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=tony.luck@intel.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®