From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/4] arm64/signal: Flush FPSIMD register state when disabling streaming mode
Date: Wed, 17 Aug 2022 15:09:46 +0100 [thread overview]
Message-ID: <Yvz2qu24hEEuqWRK@arm.com> (raw)
In-Reply-To: <20220815132834.229769-3-broonie@kernel.org>
On Mon, Aug 15, 2022 at 02:28:32PM +0100, Mark Brown wrote:
> When handling a signal delivered to a context with streaming mode enabled
> we will disable streaming mode for the signal handler, when doing so we
> should also flush the saved FPSIMD register state like exiting streaming
> mode in the hardware would do so that if that state is reloaded we get the
> same behaviour. Without this we will reload whatever the last FPSIMD state
> that was saved for the task was.
>
> Fixes: 40a8e87bb3285 ("arm64/sme: Disable ZA and streaming mode when handling signals")
> Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
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:[~2022-08-17 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 13:28 [PATCH v2 0/4] arm64/sme: SME related fixes Mark Brown
2022-08-15 13:28 ` [PATCH v2 1/4] arm64/signal: Raise limit on stack frames Mark Brown
2022-08-17 14:04 ` Catalin Marinas
2022-08-17 15:24 ` Mark Brown
2022-08-15 13:28 ` [PATCH v2 2/4] arm64/signal: Flush FPSIMD register state when disabling streaming mode Mark Brown
2022-08-17 14:09 ` Catalin Marinas [this message]
2022-08-15 13:28 ` [PATCH v2 3/4] arm64/sme: Don't flush SVE register state when allocating SME storage Mark Brown
2022-08-17 14:27 ` Catalin Marinas
2022-08-15 13:28 ` [PATCH v2 4/4] arm64/sme: Don't flush SVE register state when handling SME traps Mark Brown
2022-08-17 14:28 ` Catalin Marinas
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=Yvz2qu24hEEuqWRK@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 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.