From: Mark Rutland <mark.rutland@arm.com>
To: Ren Zhijie <renzhijie2@huawei.com>
Cc: catalin.marinas@arm.com, will@kernel.org, yusongping@huawei.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: armv8_deprecated: fix unused-function error
Date: Wed, 23 Nov 2022 11:01:28 +0000 [thread overview]
Message-ID: <Y339iLo9KQslAWht@FVFF77S0Q05N> (raw)
In-Reply-To: <28a90ac0-dc8f-f0dd-74d8-d2884e2cbd30@huawei.com>
On Wed, Nov 23, 2022 at 10:06:03AM +0800, Ren Zhijie wrote:
>
> 在 2022/11/23 0:48, Mark Rutland 写道:
> > On Tue, Nov 22, 2022 at 03:20:10AM +0000, Ren Zhijie wrote:
> > > If CONFIG_SWP_EMULATION is not set and
> > > CONFIG_CP15_BARRIER_EMULATION is not set,
> > > aarch64-linux-gnu complained about unused-function :
> > >
> > > arch/arm64/kernel/armv8_deprecated.c:67:21: error: ‘aarch32_check_condition’ defined but not used [-Werror=unused-function]
> > > static unsigned int aarch32_check_condition(u32 opcode, u32 psr)
> > > ^~~~~~~~~~~~~~~~~~~~~~~
> > > cc1: all warnings being treated as errors
> > >
> > > To fix this error, warp the definition of
> > > aarch32_check_condition() by defined(CONFIG_SWP_EMULATION) ||
> > > defined(CONFIG_CP15_BARRIER_EMULATION)
> > >
> > > Fixes: 0c5f416219da ("arm64: armv8_deprecated: move aarch32 helper earlier")
> > This also depends on building with additional options to turn warnings into
> > errors, no?
>
> No,i just run the normal command as follow:
>
> make ARCH="arm64" CROSS_COMPILE="aarch64-linux-gnu-"
I think you must also have CONFIG_WERROR enabled?
Just building defconfig + CONFIG_ARMV8_DEPRECATED=y gives me a warning, but not
an error, and the kernel builds just fine.
So this is a problem to fix, and I appreciate that in test configs this might
be broken, but it's not a full build-time failure for most users.
Thanks,
Mark.
> > > Signed-off-by: Ren Zhijie <renzhijie2@huawei.com>
> > > ---
> > > arch/arm64/kernel/armv8_deprecated.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/arch/arm64/kernel/armv8_deprecated.c b/arch/arm64/kernel/armv8_deprecated.c
> > > index ed0788cf6bbb..3f29ceb6653a 100644
> > > --- a/arch/arm64/kernel/armv8_deprecated.c
> > > +++ b/arch/arm64/kernel/armv8_deprecated.c
> > > @@ -64,6 +64,7 @@ struct insn_emulation {
> > > #define ARM_OPCODE_CONDITION_UNCOND 0xf
> > > +#if defined(CONFIG_SWP_EMULATION) || defined(CONFIG_CP15_BARRIER_EMULATION)
> > > static unsigned int aarch32_check_condition(u32 opcode, u32 psr)
> > > {
> > > u32 cc_bits = opcode >> 28;
> > > @@ -76,6 +77,7 @@ static unsigned int aarch32_check_condition(u32 opcode, u32 psr)
> > > }
> > > return ARM_OPCODE_CONDTEST_UNCOND;
> > > }
> > > +#endif
> > Could we mark this as '__maybe_unused' or 'inline' instead? I think that's
> > preferable to the ifdeferry.
>
> sure, i will use __maybe_unused in v2.
>
> Thanks,
>
> Ren.
>
> > Thanks,
> > Mark.
> >
> > > #ifdef CONFIG_SWP_EMULATION
> > > /*
> > > --
> > > 2.17.1
> > >
> > .
next prev parent reply other threads:[~2022-11-23 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 3:20 [PATCH] arm64: armv8_deprecated: fix unused-function error Ren Zhijie
2022-11-22 16:48 ` Mark Rutland
2022-11-23 2:06 ` Ren Zhijie
2022-11-23 11:01 ` Mark Rutland [this message]
2022-11-24 2:17 ` Ren Zhijie
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=Y339iLo9KQslAWht@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=renzhijie2@huawei.com \
--cc=will@kernel.org \
--cc=yusongping@huawei.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