Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
	 William Roche <william.roche@oracle.com>,
	Jiaqi Yan <jiaqiyan@google.com>,
	 linmiaohe@huawei.com, ljs@kernel.org, ziy@nvidia.com,
	osalvador@kernel.org,  harry.yoo@oracle.com, willy@infradead.org,
	osalvador@suse.de,  jackmanb@google.com, hannes@cmpxchg.org,
	nao.horiguchi@gmail.com,  tony.luck@intel.com,
	wangkefeng.wang@huawei.com, jane.chu@oracle.com,
	 akpm@linux-foundation.org, muchun.song@linux.dev,
	liam@infradead.org,  duenwen@google.com, jthoughton@google.com,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org,
	rppt@kernel.org, shuah@kernel.org,  surenb@google.com,
	mhocko@suse.com, boudewijn@delta-utec.com
Subject: Re: Linux MM Alignment Session on hwpoison (was: Re: [PATCH v6 0/5] Only free healthy pages in high-order has_hwpoisoned folio)
Date: Mon, 31 Aug 2026 12:26:58 -0700 (PDT)	[thread overview]
Message-ID: <1bd6206f-fa12-9195-7b57-f8c24e235176@google.com> (raw)
In-Reply-To: <8f023b9f-53d0-0eb8-6f75-65957761cf40@google.com>

On Fri, 28 Aug 2026, David Rientjes wrote:

> Following up on this thread and the suggestion from Matthew (thank you!), 
> I think it would be useful to have a hwpoison requirements and roadmap 
> discussion on how its support is currently integrated into the core MM, 
> get an understanding of what the areas to improve are, and get a sense of 
> future work in this area that people are planning.
> 
> This particular patch series is addressing an area of interest to Google, 
> but it's also quite clear from the thread that there are multiple areas to 
> improve for hwpoison in the core MM and it wouldn't hurt to get more 
> insight into what dependencies users have on it.
> 
> I'd propose this for discussion in one of our upcoming Linux MM Alignment 
> Sessions: Wednesday, September 16 9-10am PDT (UTC-7).
> 
> No specific agenda other than to gather core MM developers with hwpoison 
> developers and discuss:
>  - where validation should live, esp with regard to the page allocator, or
>    strict invariants in the page allocator
>    + implications for the fastpath
>  - handling for folios of arbitary orders
>  - handling partial folio poisoning and split failures
>  - race conditions between memory_failure() and concurrent
>    alloc/free/compaction
>  - soft offline for pages in the pcp lists
> 
> We might even want to be bold and discuss a holistic design overhaul if 
> it's warranted.
> 
> I'll invite those on this email thread and anybody else is welcome to 
> attend as well, the announcement email goes out two days ahead of time to 
> linux-mm@kvack.org.
> 
> If the time just doesn't work for somebody who needs to attend, please 
> reach out to me separately and we can discuss other times.
> 

Due to a couple of conflicts that people have, we'll suggest doing this at 
a special time: Wednesday, September 23 9-10am PDT (UTC-7).

Please email me privately if you're essential for the dicussion and can't 
make this time.  Thank you!


  reply	other threads:[~2026-08-31 19:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 18:07 [PATCH v6 0/5] Only free healthy pages in high-order has_hwpoisoned folio Jiaqi Yan
2026-07-05 18:07 ` [PATCH v6 1/5] mm/page_alloc: introduce __free_prepared_contig_range() with fpi_t Jiaqi Yan
2026-07-17  7:17   ` Miaohe Lin
2026-07-22  9:38   ` Vlastimil Babka (SUSE)
2026-07-25  3:54   ` Matthew Wilcox
2026-08-17  0:28     ` Jiaqi Yan
2026-07-05 18:07 ` [PATCH v6 2/5] mm/page_alloc: only free healthy pages in high-order has_hwpoisoned folio Jiaqi Yan
2026-07-17  7:19   ` Miaohe Lin
2026-07-22  9:40   ` Vlastimil Babka (SUSE)
2026-07-05 18:07 ` [PATCH v6 3/5] mm/memory-failure: set has_hwpoisoned flags on dissolved HugeTLB folio Jiaqi Yan
2026-07-25  3:05   ` Jiaqi Yan
2026-07-05 18:07 ` [PATCH v6 4/5] mm/memory-failure: skip take_page_off_buddy after dissolving HWPoison HugeTLB page Jiaqi Yan
     [not found]   ` <c5d4a1e4-cc3f-5cee-2ec3-53d5eb01bbb2@huawei.com>
2026-08-17  0:29     ` Jiaqi Yan
2026-08-17  7:23       ` Miaohe Lin
2026-08-18  3:30         ` Jiaqi Yan
2026-08-18  9:06           ` Miaohe Lin
2026-07-05 18:07 ` [PATCH v6 5/5] selftests/mm: add hard memory failure anonymous HugeTLB test Jiaqi Yan
2026-07-25  3:05   ` Jiaqi Yan
2026-07-05 18:50 ` [PATCH v6 0/5] Only free healthy pages in high-order has_hwpoisoned folio Andrew Morton
2026-07-06  9:03   ` David Hildenbrand (Arm)
2026-07-25  3:06   ` Jiaqi Yan
     [not found] ` <85cb7ea8-8116-4092-8310-69b61eb8602c@kernel.org>
     [not found]   ` <ee6bcc74-0846-43f2-bcca-b1bedff74351@oracle.com>
2026-07-22  8:27     ` Vlastimil Babka (SUSE)
2026-07-22  9:03       ` Vlastimil Babka (SUSE)
2026-07-25  6:00         ` Jiaqi Yan
2026-07-25  6:52       ` Jiaqi Yan
2026-07-27 14:20       ` David Hildenbrand (Arm)
2026-07-27 18:20         ` Matthew Wilcox
2026-07-28 17:18         ` Vlastimil Babka (SUSE)
2026-08-04 19:51           ` David Hildenbrand (Arm)
2026-08-05  8:58             ` Vlastimil Babka (SUSE)
2026-08-05  9:09               ` David Hildenbrand (Arm)
2026-08-28 23:36           ` Linux MM Alignment Session on hwpoison (was: Re: [PATCH v6 0/5] Only free healthy pages in high-order has_hwpoisoned folio) David Rientjes
2026-08-31 19:26             ` David Rientjes [this message]
2026-09-07 13:46             ` Linux MM Alignment Session on hwpoison 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=1bd6206f-fa12-9195-7b57-f8c24e235176@google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=boudewijn@delta-utec.com \
    --cc=david@kernel.org \
    --cc=duenwen@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=harry.yoo@oracle.com \
    --cc=jackmanb@google.com \
    --cc=jane.chu@oracle.com \
    --cc=jiaqiyan@google.com \
    --cc=jthoughton@google.com \
    --cc=liam@infradead.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=muchun.song@linux.dev \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@kernel.org \
    --cc=osalvador@suse.de \
    --cc=rppt@kernel.org \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=tony.luck@intel.com \
    --cc=vbabka@kernel.org \
    --cc=wangkefeng.wang@huawei.com \
    --cc=william.roche@oracle.com \
    --cc=willy@infradead.org \
    --cc=ziy@nvidia.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