From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: <mark.rutland@arm.com>, <robh@kernel.org>,
<coresight@lists.linaro.org>, <devicetree@vger.kernel.org>,
<dianders@chromium.org>, <james.clark@linaro.org>,
<krzk@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <linuxarm@huawei.com>,
<mike.leach@linaro.org>, <ruanjinjie@huawei.com>,
<saravanak@google.com>, <shameerali.kolothum.thodi@huawei.com>,
<suzuki.poulose@arm.com>
Subject: Re: [PATCH 2/5] arch_topology: update CPU map to use the new API
Date: Tue, 8 Jul 2025 09:31:49 +0100 [thread overview]
Message-ID: <20250708093149.00005ed2@huawei.com> (raw)
In-Reply-To: <20250707150414.620-3-alireza.sanaee@huawei.com>
On Mon, 7 Jul 2025 16:04:11 +0100
Alireza Sanaee <alireza.sanaee@huawei.com> wrote:
> Cleans up the cpu-map generation using the created API.
>
> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
> ---
> drivers/base/arch_topology.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
> index 3ebe77566788..88970f13f684 100644
> --- a/drivers/base/arch_topology.c
> +++ b/drivers/base/arch_topology.c
> @@ -518,23 +518,23 @@ core_initcall(free_raw_capacity);
> */
> static int __init get_cpu_for_node(struct device_node *node)
> {
> + struct device_node *cpu_node __free(device_node) = NULL;
> int cpu;
> - struct device_node *cpu_node __free(device_node) =
> - of_parse_phandle(node, "cpu", 0);
>
> - if (!cpu_node)
> - return -1;
> + cpu = of_cpu_phandle_to_id(node, &cpu_node, 0);
>
> - cpu = of_cpu_node_to_id(cpu_node);
Better I think to flip logic to exit early on errors.
So taking previous review into account - something like.
struct device_node *cpu_node = NULL;
int cpu;
cpu = of_cpu_phandle_to_id(node, &cpu_node, 0);
if (cpu == -ENODEV) {
pr_info("CPU node for %pOF exist but the possible cpu range is :%*pbl\n",
cpu_node, cpumask_pr_args(cpu_possible_mask));
return -ENODEV;
} else if (cpu < 0) {
return cpu;
}
topology_parse_cpu_capacity(cpu_node, cpu);
of_node_put(cpu_node);
return cpu;
> if (cpu >= 0)
> topology_parse_cpu_capacity(cpu_node, cpu);
> - else
> + else if (cpu == -ENODEV)
> pr_info("CPU node for %pOF exist but the possible cpu range is :%*pbl\n",
> cpu_node, cpumask_pr_args(cpu_possible_mask));
> + else
> + return -1;
>
> return cpu;
> }
>
> +
Check all patches before posting for noise like this. It sneaks in as
rebases / refactors happen so you always need to eyeball for it at the end
of development.
> static int __init parse_core(struct device_node *core, int package_id,
> int cluster_id, int core_id)
> {
next prev parent reply other threads:[~2025-07-08 9:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 15:04 [PATCH 0/5] Refactoring finding CPU phandles in DT Alireza Sanaee
2025-07-07 15:04 ` [PATCH 1/5] of: add infra for finding CPU id from phandle Alireza Sanaee
2025-07-08 8:26 ` Jonathan Cameron
2025-07-07 15:04 ` [PATCH 2/5] arch_topology: update CPU map to use the new API Alireza Sanaee
2025-07-08 6:29 ` Krzysztof Kozlowski
2025-07-08 8:22 ` Jonathan Cameron
2025-07-08 8:22 ` Jonathan Cameron
2025-07-08 8:26 ` Krzysztof Kozlowski
2025-07-08 8:26 ` Krzysztof Kozlowski
2025-07-08 8:31 ` Jonathan Cameron [this message]
2025-07-07 15:04 ` [PATCH 3/5] coresight: cti: Use of_cpu_phandle_to_id for grabbing CPU id Alireza Sanaee
2025-07-08 8:36 ` Jonathan Cameron
2025-07-07 15:04 ` [PATCH 4/5] coresight: " Alireza Sanaee
2025-07-08 8:37 ` Jonathan Cameron
2025-07-07 15:04 ` [PATCH 5/5] perf/arm-dsu: refactor cpu id retrieval via new API of_cpu_phandle_to_id Alireza Sanaee
2025-07-08 8:38 ` Jonathan Cameron
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=20250708093149.00005ed2@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alireza.sanaee@huawei.com \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=james.clark@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=saravanak@google.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=suzuki.poulose@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.