From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, nathan@kernel.org, hch@lst.de,
wangkefeng.wang@huawei.com, akpm@linux-foundation.org
Subject: [failures] mm-cma-report-correct-node-id.patch removed from -mm tree
Date: Wed, 25 Oct 2023 09:42:13 -0700 [thread overview]
Message-ID: <20231025164214.2F9CAC433C7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: cma: report correct node id
has been removed from the -mm tree. Its filename was
mm-cma-report-correct-node-id.patch
This patch was dropped because it had testing failures
------------------------------------------------------
From: Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: mm: cma: report correct node id
Date: Thu, 19 Oct 2023 09:32:53 +0800
cma_declare_contiguous_nid()'s printk can show an invalid node ID:
cma: Reserved 32 MiB at 0x00000000fe000000 on node -1
Use early_pfn_to_nid() to get correct node id from base instead of the
default NUMA_NO_NODE in cma_declare_contiguous_nid(), so users will
instead see
cma: Reserved 32 MiB at 0x00000000fe000000 on node 0
Link: https://lkml.kernel.org/r/20231019013253.2792048-1-wangkefeng.wang@huawei.com
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/cma.c | 3 +++
1 file changed, 3 insertions(+)
--- a/mm/cma.c~mm-cma-report-correct-node-id
+++ a/mm/cma.c
@@ -375,6 +375,9 @@ int __init cma_declare_contiguous_nid(ph
if (ret)
goto free_mem;
+ if (nid == NUMA_NO_NODE)
+ nid = early_pfn_to_nid(PHYS_PFN(base));
+
pr_info("Reserved %ld MiB at %pa on node %d\n", (unsigned long)size / SZ_1M,
&base, nid);
return 0;
_
Patches currently in -mm which might be from wangkefeng.wang@huawei.com are
mm_types-add-virtual-and-_last_cpupid-into-struct-folio.patch
mm-add-folio_last_cpupid.patch
mm-memory-use-folio_last_cpupid-in-do_numa_page.patch
mm-huge_memory-use-folio_last_cpupid-in-do_huge_pmd_numa_page.patch
mm-huge_memory-use-folio_last_cpupid-in-__split_huge_page_tail.patch
mm-remove-page_cpupid_last.patch
mm-add-folio_xchg_access_time.patch
sched-fair-use-folio_xchg_access_time-in-numa_hint_fault_latency.patch
mm-mprotect-use-a-folio-in-change_pte_range.patch
mm-huge_memory-use-a-folio-in-change_huge_pmd.patch
mm-remove-xchg_page_access_time.patch
mm-add-folio_xchg_last_cpupid.patch
sched-fair-use-folio_xchg_last_cpupid-in-should_numa_migrate_memory.patch
mm-migrate-use-folio_xchg_last_cpupid-in-folio_migrate_flags.patch
mm-huge_memory-use-folio_xchg_last_cpupid-in-__split_huge_page_tail.patch
mm-make-finish_mkwrite_fault-static.patch
mm-convert-wp_page_reuse-and-finish_mkwrite_fault-to-take-a-folio.patch
mm-use-folio_xchg_last_cpupid-in-wp_page_reuse.patch
mm-remove-page_cpupid_xchg_last.patch
reply other threads:[~2023-10-25 16:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231025164214.2F9CAC433C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=wangkefeng.wang@huawei.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.