From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Len Brown <len.brown@intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Ian Rogers <irogers@google.com>
Subject: Re: [PATCH 2/3] topology/sysfs: export cluster attributes only if an architectures has support
Date: Mon, 29 Nov 2021 07:54:24 +0100 [thread overview]
Message-ID: <YaR5IMK3+TAhWfet@kroah.com> (raw)
In-Reply-To: <20211128212221.1069726-3-hca@linux.ibm.com>
On Sun, Nov 28, 2021 at 10:22:20PM +0100, Heiko Carstens wrote:
> The cluster_id and cluster_cpus topology sysfs attributes have been
> added with c5e22feffdd7 ("topology: Represent clusters of CPUs within
> a die").
>
> They are currently only used for x86, arm64, and riscv (via generic
> arch topology), however they are still present with bogus default
> values for all other architectures. Instead of enforcing such new
> sysfs attributes to all architectures, make them only optional visible
> if an architecture opts in by defining both the topology_cluster_id
> and topology_cluster_cpumask attributes.
>
> This is similar to what was done when the book and drawer topology
> levels were introduced: avoid useless and therefore confusing sysfs
> attributes for architectures which cannot make use of them.
>
> This should not break any existing applications, since this is a
> new interface introduced with the v5.16 merge window.
>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
> ---
> Documentation/admin-guide/cputopology.rst | 4 ++--
> drivers/base/topology.c | 8 ++++++++
> include/linux/topology.h | 2 ++
> 3 files changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/cputopology.rst b/Documentation/admin-guide/cputopology.rst
> index c68d07533c45..ad2238b41439 100644
> --- a/Documentation/admin-guide/cputopology.rst
> +++ b/Documentation/admin-guide/cputopology.rst
> @@ -11,8 +11,8 @@ Architecture-neutral, drivers/base/topology.c, exports these attributes.
> However, the book and drawer related sysfs files will only be created if
> CONFIG_SCHED_BOOK and CONFIG_SCHED_DRAWER are selected, respectively.
>
> -The die hierarchy related sysfs files will only be created if an architecture
> -provides the related macros as described below.
> +The die and cluster hierarchy related sysfs files will only be created if an
> +architecture provides the related macros as described below.
>
> CONFIG_SCHED_BOOK and CONFIG_SCHED_DRAWER are currently only used on s390,
> where they reflect the cpu and cache hierarchy.
> diff --git a/drivers/base/topology.c b/drivers/base/topology.c
> index 7fa5a7fbef25..1a288eac2c44 100644
> --- a/drivers/base/topology.c
> +++ b/drivers/base/topology.c
> @@ -50,8 +50,10 @@ define_id_show_func(die_id);
> static DEVICE_ATTR_RO(die_id);
> #endif
>
> +#ifndef topology_cluster_no_sysfs
Same comment here, do not enable an option that disables something :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-11-29 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 21:22 [PATCH 0/3] topology/sysfs: only export used sysfs attributes Heiko Carstens
2021-11-28 21:22 ` [PATCH 1/3] topology/sysfs: export die attributes only if an architectures has support Heiko Carstens
2021-11-29 6:53 ` Greg Kroah-Hartman
2021-11-28 21:22 ` [PATCH 2/3] topology/sysfs: export cluster " Heiko Carstens
2021-11-29 6:54 ` Greg Kroah-Hartman [this message]
2021-11-28 21:22 ` [PATCH 3/3] topology/sysfs: rework book and drawer topology ifdefery Heiko Carstens
2021-11-29 6:55 ` Greg Kroah-Hartman
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=YaR5IMK3+TAhWfet@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=tmricht@linux.ibm.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
Powered by JetHome