From: Mark Rutland <mark.rutland@arm.com>
To: Dawei Li <dawei.li@shingroup.cn>
Cc: will@kernel.org, yury.norov@gmail.com, linux@rasmusvillemoes.dk,
xueshuai@linux.alibaba.com, renyu.zj@linux.alibaba.com,
yangyicong@hisilicon.com, jonathan.cameron@huawei.com,
andersson@kernel.org, konrad.dybcio@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 00/10] perf: Avoid placing cpumask var on stack
Date: Wed, 3 Apr 2024 15:41:07 +0100 [thread overview]
Message-ID: <Zg1qgxqrEi3sX3CA@FVFF77S0Q05N> (raw)
In-Reply-To: <20240403125109.2054881-1-dawei.li@shingroup.cn>
On Wed, Apr 03, 2024 at 08:50:59PM +0800, Dawei Li wrote:
> Hi all,
Hi,
> This is v2 of [1] and [2] which basically eliminate cpumask var allocation
> on stack for perf subsystem.
>
> Change since v1:
> - Change from dynamic allocation to a temporary var free helper:
> cpumask_any_and_but(). [Mark]
>
> - Some minor coding style improvements, reverse chrismas tree e.g.
>
> - For cpumask_any_and_but() itself:
> - Moved to cpumask.h, just like other helpers.
> - Return value converted to unsigned int.
> - Remove EXPORT_SYMBOL, for obvious reason.
Thanks for this!
The logic all looks good; if you can spin a v3 with the updated commit messages
I reckon we can queue this up shortly.
Mark.
>
> [1]:
> https://lore.kernel.org/lkml/20240402105610.1695644-1-dawei.li@shingroup.cn/
>
> [2]:
> https://lore.kernel.org/lkml/1486381132-5610-1-git-send-email-mark.rutland@arm.com/
>
> Dawei Li (9):
> perf/alibaba_uncore_drw: Avoid placing cpumask var on stack
> perf/arm-cmn: Avoid placing cpumask var on stack
> perf/arm_cspmu: Avoid placing cpumask var on stack
> perf/arm_dsu: Avoid placing cpumask var on stack
> perf/dwc_pcie: Avoid placing cpumask var on stack
> perf/hisi_pcie: Avoid placing cpumask var on stack
> perf/hisi_uncore: Avoid placing cpumask var on stack
> perf/qcom_l2: Avoid placing cpumask var on stack
> perf/thunderx2: Avoid placing cpumask var on stack
>
> Mark Rutland (1):
> cpumask: add cpumask_any_and_but()
>
> drivers/perf/alibaba_uncore_drw_pmu.c | 10 +++-------
> drivers/perf/arm-cmn.c | 10 +++++-----
> drivers/perf/arm_cspmu/arm_cspmu.c | 8 +++-----
> drivers/perf/arm_dsu_pmu.c | 19 ++++++-------------
> drivers/perf/dwc_pcie_pmu.c | 10 ++++------
> drivers/perf/hisilicon/hisi_pcie_pmu.c | 9 ++++-----
> drivers/perf/hisilicon/hisi_uncore_pmu.c | 6 ++----
> drivers/perf/qcom_l2_pmu.c | 8 +++-----
> drivers/perf/thunderx2_pmu.c | 10 +++-------
> include/linux/cpumask.h | 23 +++++++++++++++++++++++
> 10 files changed, 56 insertions(+), 57 deletions(-)
>
> Thanks,
>
> Dawei
>
> --
> 2.27.0
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-03 14:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:50 [PATCH v2 00/10] perf: Avoid placing cpumask var on stack Dawei Li
2024-04-03 12:51 ` [PATCH v2 01/10] cpumask: add cpumask_any_and_but() Dawei Li
2024-04-03 12:51 ` [PATCH v2 02/10] perf/alibaba_uncore_drw: Avoid placing cpumask var on stack Dawei Li
2024-04-03 14:16 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 03/10] perf/arm-cmn: " Dawei Li
2024-04-03 14:23 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 04/10] perf/arm_cspmu: " Dawei Li
2024-04-03 14:21 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 05/10] perf/arm_dsu: " Dawei Li
2024-04-03 14:32 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 06/10] perf/dwc_pcie: " Dawei Li
2024-04-03 14:33 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 07/10] perf/hisi_pcie: " Dawei Li
2024-04-03 14:35 ` Mark Rutland
2024-04-05 9:52 ` Jonathan Cameron
2024-04-03 12:51 ` [PATCH v2 08/10] perf/hisi_uncore: " Dawei Li
2024-04-03 14:35 ` Mark Rutland
2024-04-05 9:53 ` Jonathan Cameron
2024-04-03 12:51 ` [PATCH v2 09/10] perf/qcom_l2: " Dawei Li
2024-04-03 14:36 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 10/10] perf/thunderx2: " Dawei Li
2024-04-03 14:38 ` Mark Rutland
2024-04-03 14:41 ` Mark Rutland [this message]
2024-04-03 16:11 ` [PATCH v2 00/10] perf: " Dawei Li
2024-04-03 16:39 ` Yury Norov
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=Zg1qgxqrEi3sX3CA@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=andersson@kernel.org \
--cc=dawei.li@shingroup.cn \
--cc=jonathan.cameron@huawei.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=renyu.zj@linux.alibaba.com \
--cc=will@kernel.org \
--cc=xueshuai@linux.alibaba.com \
--cc=yangyicong@hisilicon.com \
--cc=yury.norov@gmail.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