[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <81b1f1c6-4308-41bb-9f65-f158d30f27bd@linux.alibaba.com>
Date: Wed, 22 Oct 2025 14:53:09 +0800
From: Shuai Xue <xueshuai@...ux.alibaba.com>
To: "Luck, Tony" <tony.luck@...el.com>, "Weiny, Ira" <ira.weiny@...el.com>,
"ankita@...dia.com" <ankita@...dia.com>,
"aniketa@...dia.com" <aniketa@...dia.com>, "Sethi, Vikram"
<vsethi@...dia.com>, "jgg@...dia.com" <jgg@...dia.com>,
"mochs@...dia.com" <mochs@...dia.com>,
"skolothumtho@...dia.com" <skolothumtho@...dia.com>,
"linmiaohe@...wei.com" <linmiaohe@...wei.com>,
"nao.horiguchi@...il.com" <nao.horiguchi@...il.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"david@...hat.com" <david@...hat.com>,
"lorenzo.stoakes@...cle.com" <lorenzo.stoakes@...cle.com>,
"Liam.Howlett@...cle.com" <Liam.Howlett@...cle.com>,
"vbabka@...e.cz" <vbabka@...e.cz>, "rppt@...nel.org" <rppt@...nel.org>,
"surenb@...gle.com" <surenb@...gle.com>, "mhocko@...e.com"
<mhocko@...e.com>, "bp@...en8.de" <bp@...en8.de>,
"rafael@...nel.org" <rafael@...nel.org>,
"guohanjun@...wei.com" <guohanjun@...wei.com>,
"mchehab@...nel.org" <mchehab@...nel.org>, "lenb@...nel.org"
<lenb@...nel.org>, "Tian, Kevin" <kevin.tian@...el.com>,
"alex@...zbot.org" <alex@...zbot.org>
Cc: "cjia@...dia.com" <cjia@...dia.com>,
"kwankhede@...dia.com" <kwankhede@...dia.com>,
"targupta@...dia.com" <targupta@...dia.com>,
"zhiw@...dia.com" <zhiw@...dia.com>, "dnigam@...dia.com"
<dnigam@...dia.com>, "kjaju@...dia.com" <kjaju@...dia.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"Jonathan.Cameron@...wei.com" <Jonathan.Cameron@...wei.com>,
"Smita.KoralahalliChannabasappa@....com"
<Smita.KoralahalliChannabasappa@....com>,
"u.kleine-koenig@...libre.com" <u.kleine-koenig@...libre.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: Re: [PATCH v3 2/3] mm: Change ghes code to allow poison of non-struct
pfn
在 2025/10/22 01:19, Luck, Tony 写道:
>>> pfn = PHYS_PFN(physical_addr);
>>> - if (!pfn_valid(pfn) && !arch_is_platform_page(physical_addr)) {
>>
>> Tony,
>>
>> I'm not an SGX expert but does this break SGX by removing
>> arch_is_platform_page()?
>>
>> See:
>>
>> 40e0e7843e23 ("x86/sgx: Add infrastructure to identify SGX EPC pages")
>> Cc: Tony Luck <tony.luck@...el.com>
>>
> Ira,
>
> I think this deletion makes the GHES code always call memory_failure()
> instead of bailing out here on "bad" page frame numbers.
>
> That centralizes the checks for different types of memory into
> memory_failure().
>
> -Tony
Hi, Tony, Ankit and Ira,
Finally, we're seeing other use cases that need to handle errors for
non-struct page PFNs :)
IMHO, non-struct page PFNs are common in production environments.
Besides NVIDIA Grace GPU device memory, we also use reserved DRAM memory
managed by a separate VMEM allocator. This VMEM allocator is designed
for virtual machine memory allocation, significantly reducing kernel
memory management overhead by minimizing page table maintenance.
To enable hardware error isolation for these memory pages, we've already
removed this sanity check internally. This change makes memory_failure()
the central point for handling all memory types, which is a much cleaner
architecture.
Reviewed-by: Shuai Xue <xueshuai@...ux.alibaba.com>
Thanks.
Shuai
Powered by blists - more mailing lists