From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH v2 0/4] arm64/sme: SME related fixes
Date: Mon, 15 Aug 2022 14:28:30 +0100 [thread overview]
Message-ID: <20220815132834.229769-1-broonie@kernel.org> (raw)
This series collates together a number of SME related fixes that have
come up in testing.
v2:
- Rebase onto v6.0-rc1.
- Fix allnoconfig build.
Mark Brown (4):
arm64/signal: Raise limit on stack frames
arm64/signal: Flush FPSIMD register state when disabling streaming
mode
arm64/sme: Don't flush SVE register state when allocating SME storage
arm64/sme: Don't flush SVE register state when handling SME traps
arch/arm64/include/asm/fpsimd.h | 4 ++--
arch/arm64/kernel/fpsimd.c | 21 ++++++---------------
arch/arm64/kernel/ptrace.c | 6 +++---
arch/arm64/kernel/signal.c | 14 ++++++++++++--
4 files changed, 23 insertions(+), 22 deletions(-)
base-commit: 568035b01cfb107af8d2e4bd2fb9aea22cf5b868
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-08-15 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 13:28 Mark Brown [this message]
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
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=20220815132834.229769-1-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).