linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RESEND v1] mm/memory_hotplug: move debug_pagealloc_map_pages() into online_pages_range()
Date: Tue, 3 Dec 2024 16:28:39 +0100	[thread overview]
Message-ID: <Z08jp0KSh6Hw_eJt@localhost.localdomain> (raw)
In-Reply-To: <20241203102050.223318-1-david@redhat.com>

On Tue, Dec 03, 2024 at 11:20:50AM +0100, David Hildenbrand wrote:
> In the near future, we want to have a single way to handover PageOffline
> pages to the buddy, whereby they could have:
> 
> (a) Never been exposed to the buddy before: kept PageOffline when onlining
>     the memory block.
> (b) Been allocated from the buddy, for example using
>     alloc_contig_range() to then be set PageOffline,
> 
> Let's start by making generic_online_page() less special compared to

This got me confused for a moment. I'd have said "making
__free_pages_core" less special? As that is where we were calling 
debug_pagealloc_map_pages() if the context  on the context.

> ordinary page freeing (e.g., free_contig_range()), and perform the
> debug_pagealloc_map_pages() call unconditionally, even when the online
> callback might decide to keep the pages offline.
> 
> All pages are already initialized with PageOffline, so nobody touches
> them either way.
> 
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Oscar Salvador <osalvador@suse.de>
> Signed-off-by: David Hildenbrand <david@redhat.com>

Acked-by: Oscar Salvador <osalvador@suse.de>


-- 
Oscar Salvador
SUSE Labs


  reply	other threads:[~2024-12-03 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 10:20 David Hildenbrand
2024-12-03 15:28 ` Oscar Salvador [this message]
2024-12-04  9:46   ` David Hildenbrand

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=Z08jp0KSh6Hw_eJt@localhost.localdomain \
    --to=osalvador@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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