From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
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 12:37:54 +0200 [thread overview]
Message-ID: <YHlpAvTPuRZtKo0i@localhost.localdomain> (raw)
In-Reply-To: <df8220ac-4214-5ff6-0048-35553fea8c8c@redhat.com>
On Fri, Apr 16, 2021 at 12:33:34PM +0200, David Hildenbrand wrote:
> IIRC, we have to add the zero shadow first, before touching the memory. This
> is also what mm/memremap.c does.
>
> In mhp_deinit_memmap_on_memory(), you already remove in the proper
> (reversed) order :)
But looking at online_pages(), we do it after the
move_pfn_range_to_zone(), right? AFAIK (I might be well wrong here),
memory_notify() will eventually call kasan_add_zero_shadow? So that
comes after the move_pfn_range_to_zone? Or is my understanding
incorrect?
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2021-04-16 10:38 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 [this message]
2021-04-16 10:51 ` David Hildenbrand
2021-04-16 11:01 ` Oscar Salvador
2021-04-16 11:07 ` David Hildenbrand
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=YHlpAvTPuRZtKo0i@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--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).