From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>,
Geetha sowjanya <gakula@marvell.com>,
Arnd Bergmann <arnd@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Robin Murphy <robin.murphy@arm.com>,
Yury Norov <ynorov@nvidia.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: marvell: avoid large stack variables
Date: Sun, 4 Oct 2026 23:09:13 +0100 [thread overview]
Message-ID: <179113453253.1503657.5347304408862116037.b4-ty@kernel.org> (raw)
In-Reply-To: <20260925130440.4107512-1-arnd@kernel.org>
On Fri, 25 Sep 2026 15:04:30 +0200, Arnd Bergmann wrote:
> The probe function in this driver constructs multiple large structures
> on the stack, which ends up causing a size warning:
>
> drivers/perf/marvell_cn10k_ddr_pmu.c:1168:12: error: stack frame size (1296) exceeds limit (1280) in 'cn10k_ddr_perf_probe' [-Werror,-Wframe-larger-than]
> 1168 | static int cn10k_ddr_perf_probe(struct platform_device *pdev)
> | ^
>
> [...]
Applied to arm64 (for-next/perf), thanks!
[1/1] perf: marvell: avoid large stack variables
https://git.kernel.org/arm64/c/7e17084177aa
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-10-04 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 13:04 [PATCH] perf: marvell: avoid large stack variables Arnd Bergmann
2026-09-25 13:08 ` sashiko-bot
2026-10-04 22:09 ` Will Deacon [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=179113453253.1503657.5347304408862116037.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gakula@marvell.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=ynorov@nvidia.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