From: Andreas Herrmann <aherrmann@suse.de>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: x86@kernel.org, Andreas Herrmann <aherrmann@suse.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Chen Yu <yu.c.chen@intel.com>, Len Brown <len.brown@intel.com>,
Radu Rendec <rrendec@redhat.com>,
Pierre Gondois <Pierre.Gondois@arm.com>, Pu Wen <puwen@hygon.cn>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Will Deacon <will@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
stable@vger.kernel.org, Ricardo Neri <ricardo.neri@intel.com>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] x86/cacheinfo: Set the number of leaves per CPU
Date: Fri, 1 Sep 2023 08:50:28 +0200 [thread overview]
Message-ID: <20230901065028.GG8103@alberich> (raw)
In-Reply-To: <20230805012421.7002-1-ricardo.neri-calderon@linux.intel.com>
On Fri, Aug 04, 2023 at 06:24:18PM -0700, Ricardo Neri wrote:
> Hi,
Hi Ricardo,
> This is v3 of a patchset to set the number of cache leaves independently
> for each CPU. v1 and v2 can be found here [1] and here [2].
I am on CC of your patch set and glanced through it.
Long ago I've touched related code but now I am not really up-to-date
to do a qualified review in this area. First, I would have to look
into documentation to refresh my memory etc. pp.
I've not seen (or it escaped me) information that this was tested on a
variety of machines that might be affected by this change. And there
are no Tested-by-tags.
Even if changes look simple and reasonable they can cause issues.
Thus from my POV it would be good to have some information what tests
were done. I am not asking to test on all possible systems but just
knowing which system(s) was (were) used for functional testing is of
value.
> Changes since v2:
> * This version uncovered a NULL-pointer dereference in recent changes to
> cacheinfo[3]. This dereference is observed when the system does not
> configure cacheinfo early during boot nor makes corrections later
> during CPU hotplug; as is the case in x86. Patch 1 fixes this issue.
>
> Changes since v1:
> * Dave Hansen suggested to use the existing per-CPU ci_cpu_cacheinfo
> variable. Now the global variable num_cache_leaves became useless.
> * While here, I noticed that init_cache_level() also became useless:
> x86 does not need ci_cpu_cacheinfo::num_levels.
>
> [1]. https://lore.kernel.org/lkml/20230314231658.30169-1-ricardo.neri-calderon@linux.intel.com/
> [2]. https://lore.kernel.org/all/20230424001956.21434-1-ricardo.neri-calderon@linux.intel.com/
> [3]. https://lore.kernel.org/all/20230412185759.755408-1-rrendec@redhat.com/
>
> Ricardo Neri (3):
> cacheinfo: Allocate memory for memory if not done from the primary CPU
> x86/cacheinfo: Delete global num_cache_leaves
> x86/cacheinfo: Clean out init_cache_level()
>
> arch/x86/kernel/cpu/cacheinfo.c | 50 ++++++++++++++++-----------------
> drivers/base/cacheinfo.c | 6 +++-
> 2 files changed, 30 insertions(+), 26 deletions(-)
>
> --
> 2.25.1
>
--
Regards,
Andreas
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nürnberg, Germany
GF: Ivo Totev, Andrew McDonald, Werner Knoblich
(HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2023-09-01 6:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 1:24 [PATCH v3 0/3] x86/cacheinfo: Set the number of leaves per CPU Ricardo Neri
2023-08-05 1:24 ` [PATCH v3 1/3] cacheinfo: Allocate memory for memory if not done from the primary CPU Ricardo Neri
2023-08-05 14:28 ` Radu Rendec
2023-08-07 23:12 ` Ricardo Neri
2023-08-30 11:49 ` Sudeep Holla
2023-08-30 12:13 ` Radu Rendec
2023-08-30 15:47 ` Sudeep Holla
2023-08-30 16:45 ` Radu Rendec
2023-09-12 0:30 ` Ricardo Neri
2023-08-05 1:24 ` [PATCH v3 2/3] x86/cacheinfo: Delete global num_cache_leaves Ricardo Neri
2023-08-05 1:24 ` [PATCH v3 3/3] x86/cacheinfo: Clean out init_cache_level() Ricardo Neri
2023-09-01 6:50 ` Andreas Herrmann [this message]
2023-09-01 7:52 ` [PATCH v3 0/3] x86/cacheinfo: Set the number of leaves per CPU Andreas Herrmann
2023-09-12 3:23 ` Ricardo Neri
2023-09-12 9:23 ` Andreas Herrmann
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=20230901065028.GG8103@alberich \
--to=aherrmann@suse.de \
--cc=Pierre.Gondois@arm.com \
--cc=aherrmann@suse.com \
--cc=catalin.marinas@arm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=puwen@hygon.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=ricardo.neri@intel.com \
--cc=rrendec@redhat.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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