[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251103184742.441e98e93c5ed36320c4f41a@linux-foundation.org>
Date: Mon, 3 Nov 2025 18:47:42 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: <ankita@...dia.com>
Cc: <aniketa@...dia.com>, <vsethi@...dia.com>, <jgg@...dia.com>,
<mochs@...dia.com>, <skolothumtho@...dia.com>, <linmiaohe@...wei.com>,
<nao.horiguchi@...il.com>, <david@...hat.com>,
<lorenzo.stoakes@...cle.com>, <Liam.Howlett@...cle.com>, <vbabka@...e.cz>,
<rppt@...nel.org>, <surenb@...gle.com>, <mhocko@...e.com>,
<tony.luck@...el.com>, <bp@...en8.de>, <rafael@...nel.org>,
<guohanjun@...wei.com>, <mchehab@...nel.org>, <lenb@...nel.org>,
<kevin.tian@...el.com>, <alex@...zbot.org>, <cjia@...dia.com>,
<kwankhede@...dia.com>, <targupta@...dia.com>, <zhiw@...dia.com>,
<dnigam@...dia.com>, <kjaju@...dia.com>, <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>, <linux-edac@...r.kernel.org>,
<Jonathan.Cameron@...wei.com>, <ira.weiny@...el.com>,
<Smita.KoralahalliChannabasappa@....com>, <u.kleine-koenig@...libre.com>,
<peterz@...radead.org>, <linux-acpi@...r.kernel.org>, <kvm@...r.kernel.org>
Subject: Re: [PATCH v5 0/3] mm: Implement ECC handling for pfn with no
struct page
On Sun, 2 Nov 2025 18:44:31 +0000 <ankita@...dia.com> wrote:
> Poison (or ECC) errors can be very common on a large size cluster.
> The kernel MM currently handles ECC errors / poison only on memory page
> backed by struct page. The handling is currently missing for the PFNMAP
> memory that does not have struct pages. The series adds such support.
>
> Implement a new ECC handling for memory without struct pages. Kernel MM
> expose registration APIs to allow modules that are managing the device
> to register its device memory region. MM then tracks such regions using
> interval tree.
Thanks. My knowledge of this material is weaker than usual :( But the
series looks good to my eye so I'll toss it into mm.git's mm-new branch
for some testing exposure. If that goes OK then I'll later move it
into the mm-unstable branch where it will get linux-next esposure. At
that point I'll monitor reviewer and tester feedback (please).
Powered by blists - more mailing lists