From: Catalin Marinas <catalin.marinas@arm.com>
To: kbuild-all@lists.01.org
Subject: Re: arch/arm64/kernel/fpsimd.c:1944:55: sparse: sparse: dereference of noderef expression
Date: Wed, 01 Jun 2022 17:54:40 +0100 [thread overview]
Message-ID: <YpeZ0M5we/0yzxVC@arm.com> (raw)
In-Reply-To: <YpcaTwI4SvV3IrwF@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
On Wed, Jun 01, 2022 at 09:50:39AM +0200, Mark Brown wrote:
> On Tue, May 31, 2022 at 05:57:42PM +0100, Catalin Marinas wrote:
> > This looks wrong indeed. IIUC, something like below but waiting for Mark
> > to confirm:
> >
> > diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c
> > index 819979398127..ac521b3403d6 100644
> > --- a/arch/arm64/kernel/fpsimd.c
> > +++ b/arch/arm64/kernel/fpsimd.c
> > @@ -1965,7 +1965,7 @@ void __efi_fpsimd_end(void)
> > 0,
> > SVCR_SM_MASK);
> > if (!system_supports_fa64())
> > - ffr = efi_sm_state;
> > + ffr = false;
>
> Yes, that looks right - feel free to add my Reviewed-by or I'll
> do that when I see the patch sent properly.
I'm no longer convinced that's the right fix. In __efi_fpsimd_begin(),
ffr is true if either !system_supports_fa64() or SVCR.SM is set. The FFR
state would be saved in this case.
In __efi_fpsimd_end(), shouldn't we just restore the FFR state if
efi_sm_state, irrespective of system_supports_fa64() (as it was checked
in the beginning). Something like:
diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c
index 819979398127..8bc9080adab2 100644
--- a/arch/arm64/kernel/fpsimd.c
+++ b/arch/arm64/kernel/fpsimd.c
@@ -1960,13 +1960,12 @@ void __efi_fpsimd_end(void)
* streaming mode.
*/
if (system_supports_sme()) {
- if (__this_cpu_read(efi_sm_state)) {
+ if (__this_cpu_read(efi_sm_state))
sysreg_clear_set_s(SYS_SVCR,
0,
SVCR_SM_MASK);
- if (!system_supports_fa64())
- ffr = efi_sm_state;
- }
+ else
+ ffr = false;
}
sve_load_state(sve_state + sve_ffr_offset(sve_max_vl()),
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: arch/arm64/kernel/fpsimd.c:1944:55: sparse: sparse: dereference of noderef expression
Date: Wed, 1 Jun 2022 17:54:40 +0100 [thread overview]
Message-ID: <YpeZ0M5we/0yzxVC@arm.com> (raw)
In-Reply-To: <YpcaTwI4SvV3IrwF@sirena.org.uk>
On Wed, Jun 01, 2022 at 09:50:39AM +0200, Mark Brown wrote:
> On Tue, May 31, 2022 at 05:57:42PM +0100, Catalin Marinas wrote:
> > This looks wrong indeed. IIUC, something like below but waiting for Mark
> > to confirm:
> >
> > diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c
> > index 819979398127..ac521b3403d6 100644
> > --- a/arch/arm64/kernel/fpsimd.c
> > +++ b/arch/arm64/kernel/fpsimd.c
> > @@ -1965,7 +1965,7 @@ void __efi_fpsimd_end(void)
> > 0,
> > SVCR_SM_MASK);
> > if (!system_supports_fa64())
> > - ffr = efi_sm_state;
> > + ffr = false;
>
> Yes, that looks right - feel free to add my Reviewed-by or I'll
> do that when I see the patch sent properly.
I'm no longer convinced that's the right fix. In __efi_fpsimd_begin(),
ffr is true if either !system_supports_fa64() or SVCR.SM is set. The FFR
state would be saved in this case.
In __efi_fpsimd_end(), shouldn't we just restore the FFR state if
efi_sm_state, irrespective of system_supports_fa64() (as it was checked
in the beginning). Something like:
diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c
index 819979398127..8bc9080adab2 100644
--- a/arch/arm64/kernel/fpsimd.c
+++ b/arch/arm64/kernel/fpsimd.c
@@ -1960,13 +1960,12 @@ void __efi_fpsimd_end(void)
* streaming mode.
*/
if (system_supports_sme()) {
- if (__this_cpu_read(efi_sm_state)) {
+ if (__this_cpu_read(efi_sm_state))
sysreg_clear_set_s(SYS_SVCR,
0,
SVCR_SM_MASK);
- if (!system_supports_fa64())
- ffr = efi_sm_state;
- }
+ else
+ ffr = false;
}
sve_load_state(sve_state + sve_ffr_offset(sve_max_vl()),
--
Catalin
next prev parent reply other threads:[~2022-06-01 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 22:49 arch/arm64/kernel/fpsimd.c:1944:55: sparse: sparse: dereference of noderef expression kernel test robot
2022-05-31 16:57 ` Catalin Marinas
2022-05-31 16:57 ` Catalin Marinas
2022-06-01 7:50 ` Mark Brown
2022-06-01 7:50 ` Mark Brown
2022-06-01 16:54 ` Catalin Marinas [this message]
2022-06-01 16:54 ` Catalin Marinas
2022-06-02 8:22 ` Mark Brown
2022-06-02 8:22 ` Mark Brown
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=YpeZ0M5we/0yzxVC@arm.com \
--to=catalin.marinas@arm.com \
--cc=kbuild-all@lists.01.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 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.