From: Ira Weiny <ira.weiny@intel.com>
To: Gregory Price <gourry@gourry.net>, <linux-mm@kvack.org>,
<linux-acpi@vger.kernel.org>
Cc: <kernel-team@meta.com>, <x86@kernel.org>,
<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>,
<rafael@kernel.org>, <lenb@kernel.org>, <david@redhat.com>,
<osalvador@suse.de>, <gregkh@linuxfoundation.org>,
<akpm@linux-foundation.org>, <dan.j.williams@intel.com>,
<Jonathan.Cameron@huawei.com>, <alison.schofield@intel.com>,
<rrichter@amd.com>, <rppt@kernel.org>, <gourry@gourry.net>,
<bfaccini@nvidia.com>, <haibo1.xu@intel.com>,
<dave.jiang@intel.com>, Fan Ni <fan.ni@samsung.com>
Subject: Re: [RESEND v7 3/3] acpi,srat: give memory block size advice based on CFMWS alignment
Date: Mon, 13 Jan 2025 14:59:22 -0600 [thread overview]
Message-ID: <67857eaa6e284_1863f329487@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20250113174439.1965168-4-gourry@gourry.net>
Gregory Price wrote:
> Capacity is stranded when CFMWS regions are not aligned to block size.
> On x86, block size increases with capacity (2G blocks @ 64G capacity).
>
> Use CFMWS base/size to report memory block size alignment advice.
>
> Suggested-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Gregory Price <gourry@gourry.net>
> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Acked-by: David Hildenbrand <david@redhat.com>
> Acked-by: Dan Williams <dan.j.williams@intel.com>
> Tested-by: Fan Ni <fan.ni@samsung.com>
> ---
> drivers/acpi/numa/srat.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/numa/srat.c b/drivers/acpi/numa/srat.c
> index 59fffe34c9d0..7526119fe945 100644
> --- a/drivers/acpi/numa/srat.c
> +++ b/drivers/acpi/numa/srat.c
> @@ -14,6 +14,7 @@
> #include <linux/errno.h>
> #include <linux/acpi.h>
> #include <linux/memblock.h>
> +#include <linux/memory.h>
> #include <linux/numa.h>
> #include <linux/nodemask.h>
> #include <linux/topology.h>
> @@ -425,13 +426,22 @@ static int __init acpi_parse_cfmws(union acpi_subtable_headers *header,
> {
> struct acpi_cedt_cfmws *cfmws;
> int *fake_pxm = arg;
> - u64 start, end;
> + u64 start, end, align;
> int node;
>
> cfmws = (struct acpi_cedt_cfmws *)header;
> start = cfmws->base_hpa;
> end = cfmws->base_hpa + cfmws->window_size;
>
> + /* Align memblock size to CFMW regions if possible */
> + align = 1UL << __ffs(start | end);
> + if (align >= SZ_256M) {
> + if (memory_block_advise_max_size(align) < 0)
> + pr_warn("CFMWS: memblock size advise failed\n");
I wonder if it would be good to print the return value here so the user
knows why this failed?
But either way.
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
> + } else {
> + pr_err("CFMWS: [BIOS BUG] base/size alignment violates spec\n");
> + }
> +
> /*
> * The SRAT may have already described NUMA details for all,
> * or a portion of, this CFMWS HPA range. Extend the memblks
> --
> 2.47.1
>
>
next prev parent reply other threads:[~2025-01-13 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 17:44 [RESEND v7 0/3] memory,x86,acpi: hotplug memory alignment advisement Gregory Price
2025-01-13 17:44 ` [RESEND v7 1/3] memory: implement memory_block_advise/probe_max_size Gregory Price
2025-01-13 20:51 ` Ira Weiny
2025-01-13 17:44 ` [RESEND v7 2/3] x86: probe memory block size advisement value during mm init Gregory Price
2025-01-13 20:56 ` Ira Weiny
2025-01-13 17:44 ` [RESEND v7 3/3] acpi,srat: give memory block size advice based on CFMWS alignment Gregory Price
2025-01-13 19:10 ` Rafael J. Wysocki
2025-01-13 20:59 ` Ira Weiny [this message]
2025-01-13 21:06 ` 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=67857eaa6e284_1863f329487@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=bfaccini@nvidia.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=fan.ni@samsung.com \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=haibo1.xu@intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@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=rppt@kernel.org \
--cc=rrichter@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