From: "Arnd Bergmann" <arnd@arndb.de>
To: "Doug Anderson" <dianders@chromium.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: "Catalin Marinas" <catalin.marinas@arm.com>,
"Lecopzer Chen" <lecopzer.chen@mediatek.com>,
"Pingfan Liu" <kernelfans@gmail.com>,
"Sumit Garg" <sumit.garg@linaro.org>,
"Will Deacon" <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Only HAVE_HARDLOCKUP_DETECTOR_PERF if the PMU config is enabled
Date: Tue, 23 May 2023 17:52:24 +0200 [thread overview]
Message-ID: <d651c1f2-ce77-4876-bbc4-88e014a83f35@app.fastmail.com> (raw)
In-Reply-To: <20230523073952.1.I60217a63acc35621e13f10be16c0cd7c363caf8c@changeid>
On Tue, May 23, 2023, at 16:39, Douglas Anderson wrote:
> If you try to enable the arm64 perf-based hardlockup detector but you
> don't enable CONFIG_ARM_PMU then you'll get an error:
>
> arch/arm64/kernel/watchdog_hld.c: In function
> 'arch_perf_nmi_is_available':
> arch/arm64/kernel/watchdog_hld.c:35:16: error: implicit declaration of
> function 'arm_pmu_irq_is_nmi' [-Werror=implicit-function-declaration]
> 35 | return arm_pmu_irq_is_nmi();
>
> It doesn't make sense to enable HAVE_HARDLOCKUP_DETECTOR_PERF if the
> PMU isn't enabled. Let's add a dependency. HW_PERF_EVENTS is a synonum
> for ARM_PMU and makes the most logical sense here, so add the
> dependency on that.
>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Closes: https://lore.kernel.org/r/20230522114922.1052421-1-arnd@kernel.org
> Fixes: 02ea35ee19d9 ("arm64: enable perf events based hard lockup detector")
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Still build testing it with randconfigs, but I assume it's fine.
Arnd
prev parent reply other threads:[~2023-05-23 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 14:39 Douglas Anderson
2023-05-23 15:52 ` Arnd Bergmann [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=d651c1f2-ce77-4876-bbc4-88e014a83f35@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=kernelfans@gmail.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.garg@linaro.org \
--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®