From: Sudeep Holla <sudeep.holla@arm.com>
To: yunhui cui <cuiyunhui@bytedance.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
gregkh@linuxfoundation.org, Sudeep Holla <sudeep.holla@arm.com>,
rafael@kernel.org, dakr@kernel.org, beata.michalska@arm.com,
ptsm@linux.microsoft.com, sumitg@nvidia.com,
yangyicong@hisilicon.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH v3 1/1] arch_topology: move parse_acpi_topology() to common code
Date: Mon, 22 Sep 2025 14:51:02 +0100 [thread overview]
Message-ID: <20250922-adventurous-pumpkin-booby-d4c95c@sudeepholla> (raw)
In-Reply-To: <CAEEQ3w=4aKS=p=+q4iC42Va+dMVm017R0Surxff+4R+4RjkgAg@mail.gmail.com>
On Mon, Sep 22, 2025 at 07:04:05PM +0800, yunhui cui wrote:
> Hi Sudeep,
>
> On Mon, Sep 22, 2025 at 5:01 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > On Mon, Sep 22, 2025 at 10:18:57AM +0800, yunhui cui wrote:
> > > Hi Sudeep,
> > >
> > > On Fri, Sep 19, 2025 at 10:05 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > [...]
> >
> > > >
> > > > Just thinking if it makes sense keep acpi_cpu_is_threaded generic without
> > > > the need for weak definition.
> > > >
> > > > Additional note: not sure why you haven't moved this under CONFIG_ARM64/RISCV as
> > > > done with other code.
> > > >
> > > > bool __init acpi_cpu_is_threaded(int cpu)
> > > > {
> > > > int is_threaded = acpi_pptt_cpu_is_thread(cpu);
> > > >
> > > > /*
> > > > * if the PPTT doesn't have thread information, check for architecture
> > > > * specific fallback if available
> > > > */
> > > > if (is_threaded < 0)
> > > > is_threaded = arch_cpu_is_threaded();
> > > >
> > > > return !!is_threaded;
> > > > }
> > > >
> > > > Then you can just have the define in
> > > >
> > > > #define arch_cpu_is_threaded() (read_cpuid_mpidr() & MPIDR_MT_BITMASK)
> > > >
> > > > in arch/arm64/include/asm/topology.h
> > > >
> > > > and
> > > >
> > > > +#ifndef arch_cpu_is_threaded
> > > > +#define arch_cpu_is_threaded (0)
> > > > +#endif
> > > >
> > > > in include/linux/arch_topology.h
> > > >
> > > > Thoughts ?
> > >
> > > If placed in include/linux/arch_topology.h, there is a possibility
> > > that "arch_cpu_is_threaded" will be redefined.
> > >
> >
> > Why is that a problem ? We want arch to override the default definition
> > if and when required.
>
> Because include/linux/topology.h first includes linux/arch_topology.h,
> and then includes asm/topology.h, a warning will be generated during
> compilation:
>
> In file included from ./include/linux/topology.h:37,
> from ./include/linux/gfp.h:8,
> from ./include/linux/xarray.h:16,
> from ./include/linux/list_lru.h:14,
> from ./include/linux/fs.h:14,
> from kernel/events/core.c:11:
> ./arch/arm64/include/asm/topology.h:39: warning:
> "arch_cpu_is_threaded" redefined
> 39 | #define arch_cpu_is_threaded() (read_cpuid_mpidr() & MPIDR_MT_BITMASK)
> |
> In file included from ./include/linux/topology.h:30:
> ./include/linux/arch_topology.h:94: note: this is the location of the
> previous definition
> 94 | #define arch_cpu_is_threaded() (0)
>
> Unless #undef arch_cpu_is_threaded is used in arch/arm64/include/asm/topology.h,
>
The above way of #undef first should be fine.
> So it's better to place
> #ifndef arch_cpu_is_threaded
> #define arch_cpu_is_threaded (0)
> #endif
> in include/asm-generic/topology.h.
>
I don't think asm-generic/topology.h is the right place and also you are
again better on order of inclusion.
--
Regards,
Sudeep
prev parent reply other threads:[~2025-09-22 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 8:59 [PATCH v3 0/1] Add support for parse_acpi_topology() on RISC-V Yunhui Cui
2025-09-19 8:59 ` [PATCH v3 1/1] arch_topology: move parse_acpi_topology() to common code Yunhui Cui
2025-09-19 11:43 ` Will Deacon
2025-09-19 14:04 ` Sudeep Holla
2025-09-22 2:18 ` [External] " yunhui cui
2025-09-22 9:01 ` Sudeep Holla
2025-09-22 11:04 ` yunhui cui
2025-09-22 13:51 ` 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=20250922-adventurous-pumpkin-booby-d4c95c@sudeepholla \
--to=sudeep.holla@arm.com \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=cuiyunhui@bytedance.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ptsm@linux.microsoft.com \
--cc=rafael@kernel.org \
--cc=sumitg@nvidia.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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