From: Bharata B Rao <bharata@amd.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Joshua Hahn <joshua.hahnjy@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<Jonathan.Cameron@huawei.com>, <dave.hansen@intel.com>,
<gourry@gourry.net>, <mgorman@techsingularity.net>,
<mingo@redhat.com>, <peterz@infradead.org>,
<raghavendra.kt@amd.com>, <riel@surriel.com>,
<rientjes@google.com>, <sj@kernel.org>, <weixugc@google.com>,
<willy@infradead.org>, <ying.huang@linux.alibaba.com>,
<ziy@nvidia.com>, <nifan.cxl@gmail.com>, <xuezhengchu@huawei.com>,
<yiannis@zptcorp.com>, <akpm@linux-foundation.org>,
<david@kernel.org>, <byungchul@sk.com>, <kinseyho@google.com>,
<yuanchu@google.com>, <balbirs@nvidia.com>,
<alok.rathore@samsung.com>, <shivankg@amd.com>,
<donettom@linux.ibm.com>
Subject: Re: [PATCH v8 0/8] mm: Hot page tracking and promotion infrastructure
Date: Mon, 28 Sep 2026 09:43:14 +0530 [thread overview]
Message-ID: <e0526c63-f6aa-4b4f-b5eb-1c76434a0857@amd.com> (raw)
In-Reply-To: <20260927232130.smxstw7f474k2qcl@offworld>
On 28-Sep-26 4:51 AM, Davidlohr Bueso wrote:
> On Wed, 16 Sep 2026, Bharata B Rao wrote:
>
>> On 12-Sep-26 2:38 AM, Joshua Hahn wrote:
>>> - I also found a bug where the kmigrated thread isn't created for nodes
>>> that are onlined later after boot, like CXL nodes that get onlined
>>> with memory later on. I've been using a small hack commit in
>>> pghot_memhp_callback that just checks for the MEM_ONLINE case and
>>> spawns a kmigrated thread.
>>
>> I will take care of this scenario (CXL node online after boot) in my next
>> posting.
>
> I was also running into this for chmu integration. I have been carrying the
> below in my own testing, fwiw.
>
> Thanks,
> Davidlohr
>
> -------------8<------------------------------------------
> diff --git a/mm/pghot.c b/mm/pghot.c
> index c7f523a61683..2f1e16e5091d 100644
> --- a/mm/pghot.c
> +++ b/mm/pghot.c
> @@ -602,6 +609,18 @@ static int kmigrated_run(int nid)
> return 0;
> }
>
> +static void kmigrated_stop(int nid)
> +{
> + pg_data_t *pgdat = NODE_DATA(nid);
> + struct task_struct *t;
> +
> + t = pgdat->kmigrated;
> + if (t) {
> + kthread_stop(t);
> + pgdat->kmigrated = NULL;
> + }
> +}
> +
> static void pghot_free_hot_map(struct mem_section *ms)
> {
> struct pghot_hot_map *hot_map;
> @@ -707,6 +726,58 @@ static struct notifier_block pghot_mem_notifier = {
> .priority = DEFAULT_CALLBACK_PRI,
> };
>
> +/*
> + * The first memory block of a node is onlined before the node gets
> + * assigned to a memory tier (memory tiers react to
> + * NODE_ADDED_FIRST_MEMORY at MEMTIER_HOTPLUG_PRI), so at
> + * MEM_GOING_ONLINE time for that block node_is_toptier() still
> + * returns true and pghot_online_sec_hotmap() skips it. Backfill the
> + * hot maps once the node tier is known.
> + */
> +static void pghot_alloc_node_hotmaps(int nid)
> +{
> + unsigned long section_nr, s_begin, start_pfn;
> + struct mem_section *ms;
> + struct page *page;
> +
> + s_begin = next_present_section_nr(-1);
> + for_each_present_section_nr(s_begin, section_nr) {
> + ms = __nr_to_section(section_nr);
> + start_pfn = section_nr_to_pfn(section_nr);
> +
> + page = pfn_to_online_page(start_pfn);
> + if (!page || page_to_nid(page) != nid)
> + continue;
> +
> + if (rcu_access_pointer(ms->hot_map))
> + continue;
> +
> + if (pghot_alloc_hot_map(ms, nid))
> + pr_warn("pghot: no hot map for section %lu on node %d\n",
> + section_nr, nid);
> + }
> +}
> +
> +static int pghot_node_callback(struct notifier_block *self,
> + unsigned long action, void *arg)
> +{
> + struct node_notify *nn = arg;
> +
> + switch (action) {
> + case NODE_ADDED_FIRST_MEMORY:
> + if (node_is_toptier(nn->nid))
> + break;
> + pghot_alloc_node_hotmaps(nn->nid);
> + kmigrated_run(nn->nid);
> + break;
> + case NODE_REMOVED_LAST_MEMORY:
> + kmigrated_stop(nn->nid);
> + break;
> + }
> +
> + return NOTIFY_OK;
> +}
> +
I don't think we should allocate section hotmaps from node hotplug notifier
callback and let it get allocated from the already existing memory hotplug
notifier callback.
I have already taken care of node hotplug in my latest tree from which I posted
only the IBS Memory Profiler part.
https://github.com/AMDESE/linux-mm/tree/bharata/pghot-mprof-rfcv0
Regards,
Bharata.
next prev parent reply other threads:[~2026-09-28 4:13 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 5:43 Bharata B Rao
2026-07-28 5:43 ` [PATCH v8 1/8] mm: migrate: Allow misplaced migration without VMA Bharata B Rao
2026-07-28 5:43 ` [PATCH v8 2/8] mm: migrate: Add promote_misplaced_memcg_folios() Bharata B Rao
2026-07-30 6:34 ` Bharata B Rao
2026-07-28 5:43 ` [PATCH v8 3/8] mm: Hot page tracking and promotion - pghot Bharata B Rao
2026-07-31 16:14 ` Bharata B Rao
2026-09-27 23:25 ` Davidlohr Bueso
2026-09-28 4:14 ` Bharata B Rao
2026-07-28 5:43 ` [PATCH v8 4/8] mm: pghot: Precision mode for pghot Bharata B Rao
2026-07-31 16:27 ` Bharata B Rao
2026-07-28 5:43 ` [PATCH v8 5/8] mm: sched: move NUMA balancing tiering promotion to pghot Bharata B Rao
2026-08-03 8:23 ` Bharata B Rao
2026-07-28 5:43 ` [PATCH v8 6/8] x86/ibs: Move IBS caps definitions into its own header Bharata B Rao
2026-07-28 5:43 ` [PATCH v8 7/8] x86/mm/ibs: In-kernel driver for AMD IBS Memory Profiler Bharata B Rao
2026-08-04 5:00 ` Bharata B Rao
2026-07-28 5:43 ` [PATCH v8 8/8] x86/mm/ibs: Add runtime controls for IBS memprofiler Bharata B Rao
2026-08-04 5:20 ` Bharata B Rao
2026-07-28 5:55 ` [PATCH v8 0/8] mm: Hot page tracking and promotion infrastructure - microbenchmark numbers Bharata B Rao
2026-07-28 5:59 ` [PATCH v8 0/8] mm: Hot page tracking and promotion infrastructure - NAS BT Bharata B Rao
2026-07-28 6:02 ` [PATCH v8 0/8] mm: Hot page tracking and promotion infrastructure - Graph500 Bharata B Rao
2026-07-28 6:05 ` [PATCH v8 0/8] mm: Hot page tracking and promotion infrastructure - redis-memtier Bharata B Rao
2026-07-28 6:17 ` [PATCH v8 0/8] mm: Hot page tracking and promotion infrastructure - llama-bench Bharata B Rao
2026-07-28 18:14 ` [PATCH v8 0/8] mm: Hot page tracking and promotion infrastructure Andrew Morton
2026-07-28 18:24 ` Matthew Wilcox
2026-07-28 18:57 ` Gregory Price
2026-07-28 19:20 ` David Hildenbrand (Arm)
2026-07-28 19:59 ` Gregory Price
2026-07-29 11:45 ` Bharata B Rao
2026-08-10 3:38 ` Yongting Lin
2026-08-10 4:16 ` Matthew Wilcox
2026-08-10 5:35 ` Bharata B Rao
2026-08-11 7:15 ` Yongting Lin
2026-08-13 2:21 ` Gregory Price
2026-08-10 14:37 ` SJ Park
2026-08-11 6:37 ` Yongting Lin
2026-07-29 9:35 ` Bharata B Rao
2026-07-29 13:54 ` SJ Park
2026-08-04 1:23 ` SJ Park
2026-08-06 5:49 ` Bharata B Rao
2026-08-06 13:44 ` SJ Park
2026-08-10 4:46 ` Bharata B Rao
2026-08-10 14:25 ` SJ Park
2026-09-11 21:08 ` Joshua Hahn
2026-09-16 3:08 ` Bharata B Rao
2026-09-16 20:52 ` Joshua Hahn
2026-09-17 5:23 ` Bharata B Rao
2026-09-27 23:21 ` Davidlohr Bueso
2026-09-28 4:13 ` Bharata B Rao [this message]
2026-09-25 2:12 ` Davidlohr Bueso
2026-09-25 9:50 ` SJ Park
2026-09-25 16:30 ` Davidlohr Bueso
2026-09-25 16:57 ` Gregory Price
2026-09-27 15:51 ` Bharata B Rao
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=e0526c63-f6aa-4b4f-b5eb-1c76434a0857@amd.com \
--to=bharata@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alok.rathore@samsung.com \
--cc=balbirs@nvidia.com \
--cc=byungchul@sk.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=david@kernel.org \
--cc=donettom@linux.ibm.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=kinseyho@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=nifan.cxl@gmail.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=shivankg@amd.com \
--cc=sj@kernel.org \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=xuezhengchu@huawei.com \
--cc=yiannis@zptcorp.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yuanchu@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®