From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Moore, Robert" <robert.moore@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"acpica-devel@lists.linux.dev" <acpica-devel@lists.linux.dev>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Danilo Krummrich <dakr@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] ACPI/MRRM: Add "node" symlink to /sys/devices/system/memory/rangeX
Date: Wed, 12 Feb 2025 08:48:41 +0100 [thread overview]
Message-ID: <2025021231-panhandle-stonewall-ba3e@gregkh> (raw)
In-Reply-To: <SJ1PR11MB6083BF8F07A18FEF581DAAF2FCFD2@SJ1PR11MB6083.namprd11.prod.outlook.com>
On Tue, Feb 11, 2025 at 05:02:11PM +0000, Luck, Tony wrote:
> >> + if (node)
> >> + ret = sysfs_create_link(&entry->dev.kobj, &node->dev.kobj, "node");
> >
> > What is going to remove this symlink if the memory goes away? Or do
> > these never get removed?
>
> There's currently no method for runtime changes to these memory ranges. They
> are described by a static ACPI table. I need to poke the folks that came up
> with this to ask how memory hotplug will be handled (since CXL seems to be
> making that fashionable again).
ACPI should be supporting memory hotplug today, at the very least
"memory add", so surely you have some old boxes to test this with?
> > symlinks in sysfs created like this always worry me. What is going to
> > use it?
>
> <hand waves>User space tools that want to understand what the "per-region"
> monitoring and control features are actually operating on.</hand waves>
If you don't have a real user today, please don't include it now. Wait
until it is actually needed.
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-12 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 21:12 [PATCH 0/4] Add interfaces for ACPI MRRM table Tony Luck
2025-02-10 21:12 ` [PATCH 1/4] ACPICA: Define MRRM ACPI table Tony Luck
2025-02-11 12:16 ` Rafael J. Wysocki
2025-02-10 21:12 ` [PATCH 2/4] ACPI/MRRM: Create /sys/devices/system/memory/rangeX ABI Tony Luck
2025-02-11 0:21 ` Luck, Tony
2025-02-11 13:08 ` David Hildenbrand
2025-02-10 21:12 ` [PATCH 3/4] ACPI/MRRM: Add "node" symlink to /sys/devices/system/memory/rangeX Tony Luck
2025-02-11 6:51 ` Greg Kroah-Hartman
2025-02-11 13:27 ` David Hildenbrand
2025-02-11 18:05 ` Luck, Tony
2025-02-13 13:30 ` David Hildenbrand
2025-02-13 19:05 ` Luck, Tony
2025-02-11 17:02 ` Luck, Tony
2025-02-12 7:48 ` Greg Kroah-Hartman [this message]
2025-02-10 21:12 ` [PATCH 4/4] ACPI/MRRM: ABI documentation for /sys/devices/system/memory/rangeX Tony Luck
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=2025021231-panhandle-stonewall-ba3e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=acpica-devel@lists.linux.dev \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dakr@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=osalvador@suse.de \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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