From: David Hildenbrand <david@redhat.com>
To: Gregory Price <gourry@gourry.net>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-mm@kvack.org
Cc: dan.j.williams@intel.com, ira.weiny@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,
rppt@kernel.org, akpm@linux-foundation.org,
alison.schofield@intel.com, Jonathan.Cameron@huawei.com,
rrichter@amd.com, ytcoode@gmail.com, haibo1.xu@intel.com,
dave.jiang@intel.com
Subject: Re: [PATCH v2 2/3] x86: probe memblock size advisement value during mm init
Date: Mon, 21 Oct 2024 13:12:26 +0200 [thread overview]
Message-ID: <7b877356-f5c5-4996-904b-6c3b71389255@redhat.com> (raw)
In-Reply-To: <20241016192445.3118-3-gourry@gourry.net>
Am 16.10.24 um 21:24 schrieb Gregory Price:
> Systems with hotplug may provide an advisement value on what the
> memblock size should be. Probe this value when the rest of the
> configuration values are considered.
>
> The new heuristic is as follows
>
> 1) set_memory_block_size_order value if already set (cmdline param)
> 2) minimum block size if memory is less than large block limit
> 3) [new] hotplug advise: lesser of advise value or memory alignment
> 4) Max block size if system is bare-metal
> 5) Largest size that aligns to end of memory.
>
> Suggested-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Gregory Price <gourry@gourry.net>
> ---
> arch/x86/mm/init_64.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> index ff253648706f..b72923b12d99 100644
> --- a/arch/x86/mm/init_64.c
> +++ b/arch/x86/mm/init_64.c
> @@ -1439,6 +1439,7 @@ static unsigned long probe_memory_block_size(void)
> {
> unsigned long boot_mem_end = max_pfn << PAGE_SHIFT;
> unsigned long bz;
> + int order;
>
> /* If memory block size has been set, then use it */
> bz = set_memory_block_size;
> @@ -1451,6 +1452,21 @@ static unsigned long probe_memory_block_size(void)
> goto done;
> }
>
> + /* Consider hotplug advisement value (if set) */
> + order = memblock_probe_size_order();
"size_order" is a very weird name. Just return a size?
memory_block_advised_max_size()
or sth like that?
> + bz = order > 0 ? (1UL << order) : 0;
> + if (bz) {
> + /* Align down to max and up to min supported */
> + bz =
> + /* Use lesser of advisement and end of memory alignment */
> + for (; bz > MIN_MEMORY_BLOCK_SIZE; bz >>= 1) {
> + if (IS_ALIGNED(boot_mem_end, bz))
> + goto done;
This looks like duplicate code wit the loop below.
Could we refactored it into something like:
advised_max_size = memory_block_advised_max_size();
if (!advised_max_size) {
bz = MAX_BLOCK_SIZE;
if (!boot_cpu_has(X86_FEATURE_HYPERVISOR)
goto done,
} else {
bz = max(min(advised_max_size, MAX_BLOCK_SIZE), MIN_MEMORY_BLOCK_SIZE);
}
for (; bz > MIN_MEMORY_BLOCK_SIZE; bz >>= 1) {
if (IS_ALIGNED(boot_mem_end, bz))
break;
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-10-21 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 19:24 [PATCH v2 0/3] mm/memblock,x86,acpi: hotplug memory alignment advisement Gregory Price
2024-10-16 19:24 ` [PATCH v2 1/3] mm/memblock: implement memblock_advise_size_order and probe functions Gregory Price
2024-10-20 8:57 ` Mike Rapoport
2024-10-21 14:39 ` Gregory Price
2024-10-16 19:24 ` [PATCH v2 2/3] x86: probe memblock size advisement value during mm init Gregory Price
2024-10-21 11:12 ` David Hildenbrand [this message]
2024-10-21 14:46 ` Gregory Price
2024-10-21 15:57 ` David Hildenbrand
2024-10-21 16:17 ` Gregory Price
2024-10-21 16:04 ` Gregory Price
2024-10-16 19:24 ` [PATCH v2 3/3] acpi,srat: reduce memory block size if CFMWS has a smaller alignment Gregory Price
2024-10-21 9:51 ` [PATCH v2 0/3] mm/memblock,x86,acpi: hotplug memory alignment advisement David Hildenbrand
2024-10-21 14:51 ` 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=7b877356-f5c5-4996-904b-6c3b71389255@redhat.com \
--to=david@redhat.com \
--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=gourry@gourry.net \
--cc=haibo1.xu@intel.com \
--cc=hpa@zytor.com \
--cc=ira.weiny@intel.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=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rppt@kernel.org \
--cc=rrichter@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=ytcoode@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox