From: Mark Rutland <mark.rutland@arm.com>
To: Will Deacon <will@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Dave Martin <Dave.Martin@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 0/6] arm64/sme: Collected SME fixes
Date: Thu, 9 Jan 2025 17:35:00 +0000 [thread overview]
Message-ID: <Z4AIxM3fYh5WEw--@J2N7QTR9R3.cambridge.arm.com> (raw)
In-Reply-To: <20250108124957.GA9312@willie-the-truck>
On Wed, Jan 08, 2025 at 12:49:58PM +0000, Will Deacon wrote:
> On Wed, Dec 04, 2024 at 03:20:48PM +0000, Mark Brown wrote:
> > This series collects the various SME related fixes that were previously
> > posted separately. These should address all the issues I am aware of so
> > a patch which reenables the SME configuration option is also included.
> >
> > Signed-off-by: Mark Brown <broonie@kernel.org>
> > ---
> > Changes in v2:
> > - Pull simplification of the signal restore code after the SME
> > reenablement, it's not a fix but there's some code overlap.
> > - Comment updates.
> > - Link to v1: https://lore.kernel.org/r/20241203-arm64-sme-reenable-v1-0-d853479d1b77@kernel.org
>
> Mark (R), are you happy with this? I know you were digging into some
> other issues in this area but I'm not sure whether they invalidate the
> fixes here or not.
Hi Will, sorry for the delay -- this has turned out to be more fractal
than I had hoped. :(
I think some of the fixes I'm working on are going to conflict with or
supersede portions of this series (e.g. portions of ptrace and signal
handling), and I'm aware of a couple more SME-specific issues that are
not addressed here.
I'll try to get that out in the next few days, and then look at this in
a bit more detail.
Rutland.
prev parent reply other threads:[~2025-01-09 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:20 Mark Brown
2024-12-04 15:20 ` [PATCH v2 1/6] arm64/sme: Flush foreign register state in do_sme_acc() Mark Brown
2024-12-04 15:20 ` [PATCH v2 2/6] arm64/fp: Don't corrupt FPMR when streaming mode changes Mark Brown
2024-12-04 15:20 ` [PATCH v2 3/6] arm64/ptrace: Zero FPMR on streaming mode entry/exit Mark Brown
2024-12-04 15:20 ` [PATCH v2 4/6] arm64/signal: Avoid corruption of SME state when entering signal handler Mark Brown
2024-12-04 15:20 ` [PATCH v2 5/6] arm64/sme: Reenable SME Mark Brown
2024-12-10 9:35 ` Luis Machado
2024-12-04 15:20 ` [PATCH v2 6/6] arm64/signal: Consistently invalidate the in register FP state in restore Mark Brown
2025-01-08 12:49 ` [PATCH v2 0/6] arm64/sme: Collected SME fixes Will Deacon
2025-01-09 17:35 ` Mark Rutland [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=Z4AIxM3fYh5WEw--@J2N7QTR9R3.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=Dave.Martin@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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®