From: "zhijun.han" <hanzj.it@gmail.com>
To: arnd@arndb.de
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
"zhijun.han" <hanzj.it@gmail.com>
Subject: [PATCH] mm: swap the definition of CONFIG_SPARSEMEM_VMEMMAP and CONFIG_SPARSEMEM
Date: Fri, 4 Nov 2022 11:28:08 +0800 [thread overview]
Message-ID: <20221104032808.24565-1-hanzj.it@gmail.com> (raw)
CONFIG_SPARSEMEM_VMEMMAP depends on CONFIG_SPARSEMEM
When CONFIG_SPARSEMEM_VMEMMAP is enabled,
CONFIG_SPARSEMEM will be enabled too.
Causes __pfn_to_page and __page_to_pfn to be overwritten
Signed-off-by: zhijun.han <hanzj.it@gmail.com>
---
include/asm-generic/memory_model.h | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/include/asm-generic/memory_model.h b/include/asm-generic/memory_model.h
index a2c8ed60233a..e06851e0b39e 100644
--- a/include/asm-generic/memory_model.h
+++ b/include/asm-generic/memory_model.h
@@ -19,12 +19,6 @@
#define __page_to_pfn(page) ((unsigned long)((page) - mem_map) + \
ARCH_PFN_OFFSET)
-#elif defined(CONFIG_SPARSEMEM_VMEMMAP)
-
-/* memmap is virtually contiguous. */
-#define __pfn_to_page(pfn) (vmemmap + (pfn))
-#define __page_to_pfn(page) (unsigned long)((page) - vmemmap)
-
#elif defined(CONFIG_SPARSEMEM)
/*
* Note: section's mem_map is encoded to reflect its start_pfn.
@@ -41,6 +35,12 @@
struct mem_section *__sec = __pfn_to_section(__pfn); \
__section_mem_map_addr(__sec) + __pfn; \
})
+
+#elif defined(CONFIG_SPARSEMEM_VMEMMAP)
+
+/* memmap is virtually contiguous. */
+#define __pfn_to_page(pfn) (vmemmap + (pfn))
+#define __page_to_pfn(page) ((unsigned long)((page) - vmemmap))
#endif /* CONFIG_FLATMEM/SPARSEMEM */
/*
--
2.37.0 (Apple Git-136)
next reply other threads:[~2022-11-04 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 3:28 zhijun.han [this message]
2022-11-04 7:58 ` [PATCH] mm: swap the definition of CONFIG_SPARSEMEM_VMEMMAP and CONFIG_SPARSEMEM Arnd Bergmann
2022-11-04 13:04 ` kernel test robot
2022-11-04 13:14 ` kernel test robot
2022-11-04 13:45 ` kernel test robot
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=20221104032808.24565-1-hanzj.it@gmail.com \
--to=hanzj.it@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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