From: "Luck, Tony" <tony.luck@intel.com>
To: Jiaqi Yan <jiaqiyan@google.com>, Shuai Xue <xueshuai@linux.alibaba.com>
Cc: "Meyer, Kyle" <kyle.meyer@hpe.com>,
"jane.chu@oracle.com" <jane.chu@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"surenb@google.com" <surenb@google.com>,
"Anderson, Russ" <russ.anderson@hpe.com>,
"rppt@kernel.org" <rppt@kernel.org>,
"osalvador@suse.de" <osalvador@suse.de>,
"nao.horiguchi@gmail.com" <nao.horiguchi@gmail.com>,
"mhocko@suse.com" <mhocko@suse.com>,
"lorenzo.stoakes@oracle.com" <lorenzo.stoakes@oracle.com>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"david@redhat.com" <david@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Fan, Shawn" <shawn.fan@intel.com>
Subject: RE: PATCH v3 ACPI: APEI: GHES: Don't offline huge pages just because BIOS asked
Date: Thu, 18 Sep 2025 19:46:16 +0000 [thread overview]
Message-ID: <SJ1PR11MB6083CA92BB014F4BB02F50D6FC16A@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CACw3F50hU3BCP=A++Dx_V=U8PKvsTvTa1=krULxfQdeK2kVBrw@mail.gmail.com>
We have multiple ways that soft offline of memory can happen.
1) BIOS (via GHES request)
a) Old "IBM style" BIOS counting errors per-page => Probably want to offline a 4K page,
breakup a transparent huge page, likely don't want to offline a libhugetlb page.
b) New BIOS counting errors on larger structures (rank, channel) => Probably want to ignore these requests.
2) RAS_CEC
This is counting per page (with very different thresholds for Intel vs. AMD). => Same as 1(a) above?
3) /sys/devices/system/memory/soft_offline_page
a) mcelog(8) Also counting per-page. => Same as 1(a)
b) rasdaemon(8) Same as mcelog(8) => Same as 1(a)
c) Some other user agent. Up to the user who knows what this agent does. => May always want to offline?
Perhaps the sysctl option to control offline should take into account the source of the request.
Especially for users who know whether their BIOS is 1(a) or. 1(b)
-Tony
next prev parent reply other threads:[~2025-09-18 19:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 15:57 [PATCH] " Tony Luck
2025-09-04 17:25 ` Mike Rapoport
2025-09-04 18:16 ` Liam R. Howlett
2025-09-05 15:53 ` [PATCH v2] " Luck, Tony
2025-09-05 16:25 ` Liam R. Howlett
2025-09-05 18:17 ` PATCH v3 " Luck, Tony
2025-09-05 19:39 ` jane.chu
2025-09-05 19:58 ` Luck, Tony
2025-09-05 20:14 ` jane.chu
2025-09-05 20:36 ` Luck, Tony
2025-09-05 19:59 ` Jiaqi Yan
2025-09-08 19:14 ` Kyle Meyer
2025-09-08 20:01 ` Luck, Tony
2025-09-10 12:01 ` Rafael J. Wysocki
2025-09-18 3:39 ` Shuai Xue
2025-09-18 15:43 ` Jiaqi Yan
2025-09-18 18:45 ` Luck, Tony
2025-09-19 1:53 ` Shuai Xue
2025-09-18 19:46 ` Luck, Tony [this message]
2025-09-19 1:49 ` Shuai Xue
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=SJ1PR11MB6083CA92BB014F4BB02F50D6FC16A@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=david@redhat.com \
--cc=jane.chu@oracle.com \
--cc=jiaqiyan@google.com \
--cc=kyle.meyer@hpe.com \
--cc=linmiaohe@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=rafael.j.wysocki@intel.com \
--cc=rppt@kernel.org \
--cc=russ.anderson@hpe.com \
--cc=shawn.fan@intel.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=xueshuai@linux.alibaba.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