All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cheng <icheng@nvidia.com>
To: Shaikh Kamaluddin <shaikhkamal2012@gmail.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	 Jonathan Cameron <jic23@kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	 Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	 Dan Williams <djbw@kernel.org>,
	Miaohe Lin <linmiaohe@huawei.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	 Breno Leitao <leitao@debian.org>, Ira Weiny <iweiny@kernel.org>,
	Li Ming <ming.li@zohomail.com>,
	 Naoya Horiguchi <nao.horiguchi@gmail.com>,
	Suren Baghdasaryan <surenb@google.com>,
	 Michal Hocko <mhocko@suse.com>,
	Brendan Jackman <brendan.jackman@linux.dev>,
	 Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
	linux-cxl@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, David Hildenbrand <david@kernel.org>,
	 Oscar Salvador <osalvador@suse.de>,
	Kiryl Shutsemau <kas@kernel.org>, Harry Yoo <harry@kernel.org>
Subject: Re: [RFC PATCH 4/5] mm/page_alloc: Keep pre-online poison out of the buddy allocator
Date: Thu, 15 Oct 2026 15:27:54 +0800	[thread overview]
Message-ID: <atB-cL8x5CSMOHEP@MWDK4CY14F> (raw)
In-Reply-To: <20261010162017.62506-5-shaikhkamal2012@gmail.com>

On Sat, Oct 10, 2026 at 09:50:12PM +0800, Shaikh Kamaluddin wrote:
> The inherited-poison path checks initialized blocks before releasing
> them to the buddy allocator. CXL device poison discovered before
> hot-added memory is onlined is recorded separately in the pre-online
> poison registry.
> 
> Extend __free_pages_core() to send a block to free_poisoned_block() when
> it intersects either poison source. In free_poisoned_block(), withhold a
> page when its PFN is registered as pre-online poison or its physical
> address is present in the inherited-poison table.
> 
> Pages identified by either source continue through
> hwpoison_boot_page(), while clean pages are released through
> accept_and_free_block().
> 
> Signed-off-by: Shaikh Kamaluddin <shaikhkamal2012@gmail.com>
> ---
>  mm/page_alloc.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index cca67a2702a4..57843df01b2a 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -33,6 +33,7 @@
>  #include <linux/cpuset.h>
>  #include <linux/folio_batch.h>
>  #include <linux/memory_hotplug.h>
> +#include <linux/memory-failure.h>
>  #include <linux/nodemask.h>
>  #include <linux/vmstat.h>
>  #include <linux/fault-inject.h>
> @@ -1601,12 +1602,14 @@ static void __meminit free_poisoned_block(struct page *page, unsigned int order,
>  					  enum meminit_context context)
>  {
>  	unsigned long i, nr_pages = 1UL << order;
> +	unsigned long pfn = page_to_pfn(page);
>  
>  	for (i = 0; i < nr_pages; i++) {
>  		struct page *p = page + i;
>  		phys_addr_t phys = page_to_phys(p);
>  
> -		if (range_contains_poisoned_memory(phys, PAGE_SIZE)) {
> +		if (range_contains_poisoned_memory(phys, PAGE_SIZE) ||
> +		    preonline_hwpoison_contains(pfn + i)) {
>  			hwpoison_boot_page(p, context);
>  			continue;
>  		}
> @@ -1652,7 +1655,8 @@ void __meminit __free_pages_core(struct page *page, unsigned int order,
>  
>  	/* First: a block parked by __free_unaccepted() never returns here. */
>  	if (range_contains_poisoned_memory(page_to_phys(page),
> -					   PAGE_SIZE << order)) {
> +					   PAGE_SIZE << order) ||
> +	    preonline_hwpoison_intersects(page_to_pfn(page), nr_pages)) {
>  		free_poisoned_block(page, order, context);
>  		return;
>  	}
> -- 
> 2.43.0
>

Hi Shaikh,

I think the idea of discovering device poison first is good, but the boundary
should be more strictly designed.

Now if I don't get it wrong, if we turn on memory_hotplug.memmap_on_memory,
we can have part of CXL memory to do the bookkeeping for itself, without
using the existing RAM.

What if that bookkeeping part is poisoned ? the check ignores this situation
right ?

What about draw a clear line between normal RAM and hot-add CXL memory, have
the latter gone through the thorough check and do the rest you want ?

Best regards,
Richard Cheng.









 


  reply	other threads:[~2026-10-15  7:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 16:20 [RFC PATCH 0/5] cxl, mm: Keep device-reported poison out of the page allocator Shaikh Kamaluddin
2026-10-10 16:20 ` [RFC PATCH 1/5] cxl/mbox: Add Get Poison List snapshot support Shaikh Kamaluddin
2026-10-10 16:38   ` sashiko-bot
2026-10-10 16:20 ` [RFC PATCH 2/5] cxl/region: Factor decoder poison-list retrieval Shaikh Kamaluddin
2026-10-10 16:34   ` sashiko-bot
2026-10-16 22:21   ` Jonathan Cameron
2026-10-10 16:20 ` [RFC PATCH 3/5] mm/memory-failure: Add a pre-online poison registry Shaikh Kamaluddin
2026-10-10 16:20 ` [RFC PATCH 4/5] mm/page_alloc: Keep pre-online poison out of the buddy allocator Shaikh Kamaluddin
2026-10-15  7:27   ` Richard Cheng [this message]
2026-10-10 16:20 ` [RFC PATCH 5/5] cxl/region: Register device poison before exposing RAM Shaikh Kamaluddin
2026-10-10 16:33   ` sashiko-bot
2026-10-15  7:59   ` Richard Cheng
2026-10-16 22:35   ` Jonathan Cameron
2026-10-16 20:42 ` [RFC PATCH 0/5] cxl, mm: Keep device-reported poison out of the page allocator Jonathan Cameron

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=atB-cL8x5CSMOHEP@MWDK4CY14F \
    --to=icheng@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=alison.schofield@intel.com \
    --cc=brendan.jackman@linux.dev \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=david@kernel.org \
    --cc=djbw@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=harry@kernel.org \
    --cc=iweiny@kernel.org \
    --cc=jic23@kernel.org \
    --cc=kas@kernel.org \
    --cc=leitao@debian.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=ming.li@zohomail.com \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    --cc=shaikhkamal2012@gmail.com \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=vishal.l.verma@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.