mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Michal Hocko <mhocko@suse.com>, Kyle Meyer <kyle.meyer@hpe.com>
Cc: akpm@linux-foundation.org, corbet@lwn.net, linmiaohe@huawei.com,
	shuah@kernel.org, tony.luck@intel.com, jane.chu@oracle.com,
	jiaqiyan@google.com, Liam.Howlett@oracle.com, bp@alien8.de,
	hannes@cmpxchg.org, jack@suse.cz, joel.granados@kernel.org,
	laoar.shao@gmail.com, lorenzo.stoakes@oracle.com,
	mclapinski@google.com, nao.horiguchi@gmail.com,
	osalvador@suse.de, rafael.j.wysocki@intel.com, rppt@kernel.org,
	russ.anderson@hpe.com, shawn.fan@intel.com, surenb@google.com,
	vbabka@suse.cz, linux-acpi@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3] mm/memory-failure: Support disabling soft offline for HugeTLB pages
Date: Wed, 16 Sep 2026 15:08:45 +0200	[thread overview]
Message-ID: <ad36cd54-7319-4bb4-bf8f-9fcc7b009158@kernel.org> (raw)
In-Reply-To: <aqpYxAktjexhaMGc@tiehlicka>


> 
> OK, so apparently there are some BIOSes which abuse this feature to
> mimic a real HW poisoning. This doesn't change the overall picture
> though

Is this really abusing? We know that a page is shaky and will likely go bad in
the future, For now it is still accessible. Trying to migrate off that page stop
using it right away sounds pretty logical to me.

Now, the weird thing is that for hugetlb we wants a different behavior (keep
using the page and ignore the request to evacuate).

> 
>> If you think this should be handled differently, I'm open to suggestions.
> 
> Yes, do not treat hugetlb pages any special. In case there is a HW
> related problem which decides to offline portion of the hugetlb page
> then bad for you. It wouldn't be too much different if this was handled
> through a real HW poisoning.

I agree with that.

-- 
Cheers,

David

  reply	other threads:[~2026-09-16 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 23:49 Kyle Meyer
2026-09-15  0:37 ` Andrew Morton
2026-09-15  0:57   ` Kyle Meyer
2026-09-15  8:31 ` Michal Hocko
2026-09-15 17:55   ` Kyle Meyer
2026-09-16  8:52     ` Michal Hocko
2026-09-16 13:08       ` David Hildenbrand (Arm) [this message]
2026-09-16 13:19         ` Michal Hocko
2026-09-16 13:28           ` David Hildenbrand (Arm)
2026-09-16 13:45             ` Michal Hocko
2026-09-16 14:30               ` David Hildenbrand (Arm)

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=ad36cd54-7319-4bb4-bf8f-9fcc7b009158@kernel.org \
    --to=david@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=jack@suse.cz \
    --cc=jane.chu@oracle.com \
    --cc=jiaqiyan@google.com \
    --cc=joel.granados@kernel.org \
    --cc=kyle.meyer@hpe.com \
    --cc=laoar.shao@gmail.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mclapinski@google.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=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=tony.luck@intel.com \
    --cc=vbabka@suse.cz \
    /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®