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 1/3] memory: implement memory_block_advise/probe_max_size
Date: Fri, 1 Nov 2024 18:02:03 +0200 [thread overview]
Message-ID: <ZyT7e3xS2p6DqGYO@kernel.org> (raw)
In-Reply-To: <20241101134706.1185-2-gourry@gourry.net>
On Fri, Nov 01, 2024 at 09:47:03AM -0400, Gregory Price wrote:
> Hotplug memory sources may have opinions on what the memblock size
> should be - usually for alignment purposes. For example, CXL memory
> extents can be 256MB with a matching alignment. If this size/alignment
> is smaller than the block size, it can result in stranded capacity.
>
> Implement memory_block_advise_max_size for use prior to allocator init,
> for software to advise the system on the max block size.
>
> Implement memory_block_probe_max_size for use by arch init code to
> calculate the best block size. Use of advice is architecture defined.
>
> The probe value can never change after first probe. Calls to advise
> after probe will return -EBUSY to aid debugging.
>
> On systems without hotplug, always return -ENODEV and 0 respectively.
>
> Suggested-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Gregory Price <gourry@gourry.net>
> Acked-by: David Hildenbrand <david@redhat.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> drivers/base/memory.c | 53 ++++++++++++++++++++++++++++++++++++++++++
> include/linux/memory.h | 10 ++++++++
> 2 files changed, 63 insertions(+)
>
> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
> index 67858eeb92ed..835793150b41 100644
> --- a/drivers/base/memory.c
> +++ b/drivers/base/memory.c
> @@ -110,6 +110,59 @@ static void memory_block_release(struct device *dev)
> kfree(mem);
> }
>
> +
> +/* Max block size to be set by memory_block_advise_max_size */
> +static unsigned long memory_block_advised_size;
> +static bool memory_block_advised_size_queried;
> +
> +/**
> + * memory_block_advise_max_size() - advise memory hotplug on the max suggested
> + * block size, usually for alignment.
> + * @size: suggestion for maximum block size. must be aligned on power of 2.
> + *
> + * Early boot software (pre-allocator init) may advise archs on the max block
> + * size. This value can only decrease after initialization, as the intent is
> + * to identify the largest supported alignment for all sources.
> + *
> + * Use of this value is arch-defined, as is min/max block size.
> + *
> + * Return: 0 on success
> + * -EINVAL if size is 0 or not pow2 aligned
> + * -EBUSY if value has already been probed
> + */
> +int __init memory_block_advise_max_size(unsigned long size)
> +{
> + if (!size || !is_power_of_2(size))
> + return -EINVAL;
> +
> + if (memory_block_advised_size_queried)
> + return -EBUSY;
> +
> + if (memory_block_advised_size) {
> + memory_block_advised_size = min(memory_block_advised_size,
> + size);
> + } else {
> + memory_block_advised_size = size;
> + }
> +
> + return 0;
> +}
> +
> +/**
> + * memory_block_advised_max_size() - query advised max hotplug block size.
> + *
> + * After the first call, the value can never change. Callers looking for the
> + * actual block size should use memory_block_size_bytes. This interface is
> + * intended for use by arch-init when initializing the hotplug block size.
> + *
> + * Return: advised size in bytes, or 0 if never set.
> + */
> +unsigned long memory_block_advised_max_size(void)
> +{
> + memory_block_advised_size_queried = true;
> + return memory_block_advised_size;
> +}
> +
> unsigned long __weak memory_block_size_bytes(void)
> {
> return MIN_MEMORY_BLOCK_SIZE;
> diff --git a/include/linux/memory.h b/include/linux/memory.h
> index c0afee5d126e..8202d0efbf46 100644
> --- a/include/linux/memory.h
> +++ b/include/linux/memory.h
> @@ -149,6 +149,14 @@ static inline int hotplug_memory_notifier(notifier_fn_t fn, int pri)
> {
> return 0;
> }
> +static inline int memory_block_advise_max_size(unsigned long size)
> +{
> + return -ENODEV;
> +}
> +static inline unsigned long memory_block_advised_max_size(void)
> +{
> + return 0;
> +}
> #else /* CONFIG_MEMORY_HOTPLUG */
> extern int register_memory_notifier(struct notifier_block *nb);
> extern void unregister_memory_notifier(struct notifier_block *nb);
> @@ -181,6 +189,8 @@ int walk_dynamic_memory_groups(int nid, walk_memory_groups_func_t func,
> void memory_block_add_nid(struct memory_block *mem, int nid,
> enum meminit_context context);
> #endif /* CONFIG_NUMA */
> +int memory_block_advise_max_size(unsigned long size);
> +unsigned long memory_block_advised_max_size(void);
> #endif /* CONFIG_MEMORY_HOTPLUG */
>
> /*
> --
> 2.43.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2024-11-01 16:06 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 [this message]
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
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=ZyT7e3xS2p6DqGYO@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox