From: Mike Rapoport <rppt@kernel.org>
To: Gregory Price <gourry@gourry.net>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-mm@kvack.org,
linux-cxl@vger.kernel.org, Jonathan.Cameron@huawei.com,
dan.j.williams@intel.com, rrichter@amd.com, Terry.Bowman@amd.com,
dave.jiang@intel.com, ira.weiny@intel.com,
alison.schofield@intel.com, 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
Subject: Re: [PATCH v5 3/3] acpi,srat: give memory block size advice based on CFMWS alignment
Date: Fri, 1 Nov 2024 18:03:02 +0200 [thread overview]
Message-ID: <ZyT7ttLG-_eGMDmx@kernel.org> (raw)
In-Reply-To: <20241101134706.1185-4-gourry@gourry.net>
On Fri, Nov 01, 2024 at 09:47:05AM -0400, 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>
> ---
> 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 44f91f2c6c5d..34b6993e7d6c 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>
> @@ -338,13 +339,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");
> + } 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.43.0
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2024-11-01 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 13:47 [PATCH v5 0/3] memory,x86,acpi: hotplug memory alignment advisement Gregory Price
2024-11-01 13:47 ` [PATCH v5 1/3] memory: implement memory_block_advise/probe_max_size Gregory Price
2024-11-01 16:02 ` Mike Rapoport
2024-11-01 13:47 ` [PATCH v5 2/3] x86: probe memory block size advisement value during mm init Gregory Price
2024-11-01 15:22 ` Dave Hansen
2024-11-01 15:51 ` Borislav Petkov
2024-11-01 16:19 ` Gregory Price
2024-11-01 16:48 ` Borislav Petkov
2024-11-01 16:02 ` Mike Rapoport
2024-11-01 13:47 ` [PATCH v5 3/3] acpi,srat: give memory block size advice based on CFMWS alignment Gregory Price
2024-11-01 16:03 ` Mike Rapoport [this message]
2024-11-04 9:11 ` David Hildenbrand
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=ZyT7ttLG-_eGMDmx@kernel.org \
--to=rppt@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Terry.Bowman@amd.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=gourry@gourry.net \
--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=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 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.