From: Gregory Price <gourry@gourry.net>
To: linux-cxl@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org,
linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
luto@kernel.org, peterz@infradead.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com, david@redhat.com,
osalvador@suse.de, gregkh@linuxfoundation.org, rafael@kernel.org,
akpm@linux-foundation.org, dan.j.williams@intel.com,
Jonathan.Cameron@Huawei.com, alison.schofield@intel.com,
rrichter@amd.com, terry.bowman@amd.com, lenb@kernel.org,
dave.jiang@intel.com, ira.weiny@intel.com
Subject: [PATCH 2/3] x86/mm: if memblock size is adjusted, update the cached value
Date: Tue, 8 Oct 2024 00:43:54 -0400 [thread overview]
Message-ID: <20241008044355.4325-3-gourry@gourry.net> (raw)
In-Reply-To: <20241008044355.4325-1-gourry@gourry.net>
When parsing CFMWS, we need to know the currently registered memory
block size to avoid accidentally adjusting the size upward. Querying
the size causes it to be cached in a static global. Update the static
global if the value is subsequently updated.
Print a warning that this has occurred for debugging purposes if
the memory block size is changed at an unexpected time (post-init).
Signed-off-by: Gregory Price <gourry@gourry.net>
---
arch/x86/mm/init_64.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 6086f99449fa..733dfa899232 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -1424,6 +1424,7 @@ void mark_rodata_ro(void)
/* Adjustable memory block size */
static unsigned long set_memory_block_size;
+static unsigned long memory_block_size_probed;
int set_memory_block_size_order(unsigned int order)
{
unsigned long size = 1UL << order;
@@ -1432,6 +1433,19 @@ int set_memory_block_size_order(unsigned int order)
return -EINVAL;
set_memory_block_size = size;
+
+ /*
+ * If the block size has already been probed, we need to change it.
+ * This can happen during ACPI/CFMWS parsing, since it needs to
+ * probe the system for the existing block size to avoid increasing
+ * the block size if lower memory happens to be misaligned
+ */
+ if (memory_block_size_probed) {
+ memory_block_size_probed = size;
+ pr_warn("x86/mm: Memory block size changed: %ldMB\n",
+ size >> 20);
+ }
+
return 0;
}
@@ -1471,7 +1485,6 @@ static unsigned long probe_memory_block_size(void)
return bz;
}
-static unsigned long memory_block_size_probed;
unsigned long memory_block_size_bytes(void)
{
if (!memory_block_size_probed)
--
2.43.0
next prev parent reply other threads:[~2024-10-08 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 4:43 [PATCH 0/3] memory,acpi: resize memory blocks based on CFMW alignment Gregory Price
2024-10-08 4:43 ` [PATCH 1/3] memory: extern memory_block_size_bytes and set_memory_block_size_order Gregory Price
2024-10-08 14:03 ` David Hildenbrand
2024-10-08 14:51 ` Gregory Price
2024-10-08 15:02 ` David Hildenbrand
2024-10-08 15:21 ` Gregory Price
2024-10-08 19:04 ` Ira Weiny
2024-10-08 19:45 ` Gregory Price
2024-10-14 11:54 ` David Hildenbrand
2024-10-14 14:25 ` Gregory Price
2024-10-14 20:32 ` David Hildenbrand
2024-10-14 22:40 ` Gregory Price
2024-10-08 4:43 ` Gregory Price [this message]
2024-10-08 4:43 ` [PATCH 3/3] acpi,srat: reduce memory block size if CFMWS has a smaller alignment Gregory Price
2024-10-08 14:58 ` Ira Weiny
2024-10-08 15:17 ` Gregory Price
2024-10-08 16:46 ` Dan Williams
2024-10-14 11:50 ` David Hildenbrand
2024-10-08 19:02 ` Ira Weiny
2024-10-08 14:38 ` [PATCH 0/3] memory,acpi: resize memory blocks based on CFMW alignment Ira Weiny
2024-10-08 14:49 ` Gregory Price
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=20241008044355.4325-3-gourry@gourry.net \
--to=gourry@gourry.net \
--cc=Jonathan.Cameron@Huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=ira.weiny@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=osalvador@suse.de \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rrichter@amd.com \
--cc=terry.bowman@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@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