linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Oscar Salvador <osalvador@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@kernel.org>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 4/8] mm,memory_hotplug: Allocate memmap from the added memory range
Date: Fri, 16 Apr 2021 13:07:06 +0200	[thread overview]
Message-ID: <b0f5f87c-af03-173c-17e3-ccf15ccb9cb1@redhat.com> (raw)
In-Reply-To: <YHlufVk+2O7HsXJh@localhost.localdomain>


> -int __ref online_pages(unsigned long pfn, unsigned long nr_pages,
> -		       int online_type, int nid)
> +int mhp_init_memmap_on_memory(unsigned long pfn, unsigned long nr_pages,
> +			      struct zone *zone)
> +{
> +	unsigned long end_pfn = pfn + nr_pages;
> +	int ret;
> +
> +	ret = kasan_add_zero_shadow(__va(PFN_PHYS(pfn)), PFN_PHYS(nr_pages));
> +	if (ret)
> +		return ret;
> +
> +	/*
> +	 * Initialize vmemmap pages with the corresponding node, zone links set.

The "set" sounds weird. I'd remove that comment completely.

> +	 */
> +	move_pfn_range_to_zone(zone, pfn, nr_pages, NULL, MIGRATE_UNMOVABLE);
> +
> +	/*
> +	 * It might be that the vmemmap_pages fully span sections. If that is
> +	 * the case, mark those sections online here as otherwise they will be
> +	 * left offline.
> +	 */
> +	if (nr_pages >= PAGES_PER_SECTION)
> +	        online_mem_sections(pfn, ALIGN_DOWN(end_pfn, PAGES_PER_SECTION));
> +
> +	return ret;
> +}
> +
> +void mhp_deinit_memmap_on_memory(unsigned long pfn, unsigned long nr_pages)
> +{
> +	unsigned long end_pfn = pfn + nr_pages;
> +        /*
> +	 * The pages associated with this vmemmap have been offlined, so
> +	 * we can reset its state here.
> +	 */
> +	remove_pfn_range_from_zone(page_zone(pfn_to_page(pfn)), pfn, nr_pages);
> +	kasan_remove_zero_shadow(__va(PFN_PHYS(pfn)), PFN_PHYS(nr_pages));
> +
> +	/*
> +	 * It might be that the vmemmap_pages fully span sections. If that is
> +	 * the case, mark those sections offline here as otherwise they will be
> +	 * left online.
> +	 */
> +	if (nr_pages >= PAGES_PER_SECTION)
> +		offline_mem_sections(pfn, ALIGN_DOWN(end_pfn, PAGES_PER_SECTION));

It's usually best if you undo stuff in the complete opposite order. For 
example at this point, the memmap might already have been poisoned, yet 
pfn_to_online_page() would return true. You should do that first.

Apart from that, nothing jumped at me :)

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Thanks,

David / dhildenb


  reply	other threads:[~2021-04-16 11:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 10:21 [PATCH v8 0/8] Allocate memmap from hotadded memory (per device) Oscar Salvador
2021-04-16 10:21 ` [PATCH v8 1/8] drivers/base/memory: Introduce memory_block_{online,offline} Oscar Salvador
2021-04-16 10:21 ` [PATCH v8 2/8] mm,memory_hotplug: Relax fully spanned sections check Oscar Salvador
2021-04-16 10:21 ` [PATCH v8 3/8] mm,memory_hotplug: Factor out adjusting present pages into adjust_present_page_count() Oscar Salvador
2021-04-16 10:21 ` [PATCH v8 4/8] mm,memory_hotplug: Allocate memmap from the added memory range Oscar Salvador
2021-04-16 10:33   ` David Hildenbrand
2021-04-16 10:37     ` Oscar Salvador
2021-04-16 10:51       ` David Hildenbrand
2021-04-16 11:01         ` Oscar Salvador
2021-04-16 11:07           ` David Hildenbrand [this message]
2021-04-16 10:21 ` [PATCH v8 5/8] acpi,memhotplug: Enable MHP_MEMMAP_ON_MEMORY when supported Oscar Salvador
2021-04-16 10:21 ` [PATCH v8 6/8] mm,memory_hotplug: Add kernel boot option to enable memmap_on_memory Oscar Salvador
2021-04-16 10:21 ` [PATCH v8 7/8] x86/Kconfig: Introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE Oscar Salvador
2021-04-16 10:21 ` [PATCH v8 8/8] arm64/Kconfig: " Oscar Salvador

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=b0f5f87c-af03-173c-17e3-ccf15ccb9cb1@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=osalvador@suse.de \
    --cc=pasha.tatashin@soleen.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;
as well as URLs for NNTP newsgroup(s).