From: Sudeep Holla <sudeep.holla@arm.com>
To: Pierre Gondois <pierre.gondois@arm.com>
Cc: linux-kernel@vger.kernel.org, Radu Rendec <rrendec@redhat.com>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Conor Dooley <conor.dooley@microchip.com>,
Will Deacon <will@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Palmer Dabbelt <palmer@rivosinc.com>,
Gavin Shan <gshan@redhat.com>
Subject: Re: [PATCH v3 4/4] cacheinfo: Add use_arch[|_cache]_info field/function
Date: Thu, 13 Apr 2023 11:20:05 +0100 [thread overview]
Message-ID: <20230413102005.u3ohh2mlxdsoz7ka@bogus> (raw)
In-Reply-To: <d74ee654-287a-a065-71ec-577957d86bf7@arm.com>
On Thu, Apr 13, 2023 at 12:17:09PM +0200, Pierre Gondois wrote:
>
>
> On 4/13/23 11:49, Sudeep Holla wrote:
> > On Thu, Apr 13, 2023 at 11:14:34AM +0200, Pierre Gondois wrote:
> > > The cache information can be extracted from either a Device
> > > Tree (DT), the PPTT ACPI table, or arch registers (clidr_el1
> > > for arm64).
> > >
> > > The clidr_el1 register is used only if DT/ACPI information is not
> > > available. It does not states how caches are shared among CPUs.
> > >
> > > Add a use_arch_cache_info field/function to identify when the
> > > DT/ACPI doesn't provide cache information. Use this information
> > > to assume L1 caches are privates and L2 and higher are shared among
> > > all CPUs.
> > >
> >
> > I have tentatively merged first 3 patches along with Radu's series(waiting
> > for build tests still before confirming). I am not yet sure on this.
> >
> > > Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
> > > ---
> > > drivers/base/cacheinfo.c | 13 ++++++++++++-
> > > include/linux/cacheinfo.h | 10 ++++++++++
> > > 2 files changed, 22 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/base/cacheinfo.c b/drivers/base/cacheinfo.c
> > > index 06de9a468958..49dbb4357911 100644
> > > --- a/drivers/base/cacheinfo.c
> > > +++ b/drivers/base/cacheinfo.c
> > > @@ -40,7 +40,8 @@ static inline bool cache_leaves_are_shared(struct cacheinfo *this_leaf,
> > > * For non DT/ACPI systems, assume unique level 1 caches,
> > > * system-wide shared caches for all other levels.
> > > */
> > > - if (!(IS_ENABLED(CONFIG_OF) || IS_ENABLED(CONFIG_ACPI)))
> > > + if (!(IS_ENABLED(CONFIG_OF) || IS_ENABLED(CONFIG_ACPI)) ||
> > > + this_leaf->use_arch_info)
> >
> > Can't we just use use_arch_cache_info() here ?
>
> I think that if we use use_arch_cache_info() here, then arm64 platforms
> will always return here and never check fw_token/this_leaf->id values.
> Indeed, we also need to know that no cache information is available in
> DT/ACPI, cf. [1]
>
Ah right, I missed to see that. I was sure there is a reason but couldn't
figure out myself quickly.
> >
> > > return (this_leaf->level != 1) && (sib_leaf->level != 1);
> > > if ((sib_leaf->attributes & CACHE_ID) &&
> > > @@ -349,6 +350,7 @@ static int cache_shared_cpu_map_setup(unsigned int cpu)
> > > struct cpu_cacheinfo *this_cpu_ci = get_cpu_cacheinfo(cpu);
> > > struct cacheinfo *this_leaf, *sib_leaf;
> > > unsigned int index, sib_index;
> > > + bool use_arch_info = false;
> > > int ret = 0;
> > > if (this_cpu_ci->cpu_map_populated)
> > > @@ -361,6 +363,12 @@ static int cache_shared_cpu_map_setup(unsigned int cpu)
> > > */
> > > if (!last_level_cache_is_valid(cpu)) {
> > > ret = cache_setup_properties(cpu);
> > > + if (ret && use_arch_cache_info()) {
> > > + // Possibility to rely on arch specific information.
>
> [1]
>
> > > + use_arch_info = true;
> > > + ret = 0;
> > > + }
> > > +
> > > if (ret)
> > > return ret;
> > > }
> > > @@ -370,6 +378,9 @@ static int cache_shared_cpu_map_setup(unsigned int cpu)
> > > this_leaf = per_cpu_cacheinfo_idx(cpu, index);
> > > + if (use_arch_info)
> > > + this_leaf->use_arch_info = true;
> > > +
> > > cpumask_set_cpu(cpu, &this_leaf->shared_cpu_map);
> > > for_each_online_cpu(i) {
> > > struct cpu_cacheinfo *sib_cpu_ci = get_cpu_cacheinfo(i);
> > > diff --git a/include/linux/cacheinfo.h b/include/linux/cacheinfo.h
> > > index 908e19d17f49..fed675b251a2 100644
> > > --- a/include/linux/cacheinfo.h
> > > +++ b/include/linux/cacheinfo.h
> > > @@ -66,6 +66,7 @@ struct cacheinfo {
> > > #define CACHE_ALLOCATE_POLICY_MASK \
> > > (CACHE_READ_ALLOCATE | CACHE_WRITE_ALLOCATE)
> > > #define CACHE_ID BIT(4)
> > > + bool use_arch_info;
> >
> > Do you see the need to stash this value as it is either globally true or
> > false based on the arch ?
>
> A static variable could be used instead and set to true if we fail to fetch the
> cache information from DT/ACPI, cf. [1]. The only possible transition for this
> variable would be from false->true. I'll check if this works like this.
>
Yes that would be good.
> >
> > > void *fw_token;
> > > bool disable_sysfs;
> > > void *priv;
> > > @@ -129,4 +130,13 @@ static inline int get_cpu_cacheinfo_id(int cpu, int level)
> > > return -1;
> > > }
> > > +static inline bool use_arch_cache_info(void)
> > > +{
> > > +#if defined(CONFIG_ARM64)
> > > + return true;
> > > +#else
> > > + return false;
> > > +#endif
> > > +}
> > > +
> >
> > Can we just have it as:
> > #ifdef CONFIG_ARM64
> > #define use_arch_cache_info() (true)
> > #else
> > #define use_arch_cache_info() (false)
> > #endif
>
> Yes sure, I'll post a v4 with this along Conor's requested change.
>
Sure.
--
Regards,
Sudeep
prev parent reply other threads:[~2023-04-13 10:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 9:14 [PATCH v3 0/4] cacheinfo: Correctly fallback to using clidr_el1's information Pierre Gondois
2023-04-13 9:14 ` [PATCH v3 1/4] cacheinfo: Check sib_leaf in cache_leaves_are_shared() Pierre Gondois
2023-04-13 10:04 ` Conor Dooley
2023-04-13 9:14 ` [PATCH v3 2/4] cacheinfo: Check cache properties are present in DT Pierre Gondois
2023-04-13 10:06 ` Conor Dooley
2023-04-13 18:16 ` Florian Fainelli
2023-04-13 19:50 ` Sudeep Holla
2023-04-13 20:06 ` Florian Fainelli
2023-04-14 7:33 ` Pierre Gondois
2023-04-14 9:05 ` Sudeep Holla
2023-04-14 22:21 ` Florian Fainelli
2023-04-14 8:19 ` Pierre Gondois
2023-04-13 9:14 ` [PATCH v3 3/4] arch_topology: Remove early cacheinfo error message Pierre Gondois
2023-04-13 10:02 ` Conor Dooley
2023-04-13 10:25 ` Conor Dooley
2023-04-13 15:25 ` Pierre Gondois
2023-04-13 16:23 ` Conor Dooley
2023-04-13 9:14 ` [PATCH v3 4/4] cacheinfo: Add use_arch[|_cache]_info field/function Pierre Gondois
2023-04-13 9:49 ` Sudeep Holla
2023-04-13 10:17 ` Pierre Gondois
2023-04-13 10:20 ` Sudeep Holla [this message]
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=20230413102005.u3ohh2mlxdsoz7ka@bogus \
--to=sudeep.holla@arm.com \
--cc=alexghiti@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=gshan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@rivosinc.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=rrendec@redhat.com \
--cc=will@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
all inboxes | Powered by JetHome®