[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z4AIxM3fYh5WEw--@J2N7QTR9R3.cambridge.arm.com>
Date: Thu, 9 Jan 2025 17:35:00 +0000
From: Mark Rutland <mark.rutland@....com>
To: Will Deacon <will@...nel.org>
Cc: Mark Brown <broonie@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Dave Martin <Dave.Martin@....com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v2 0/6] arm64/sme: Collected SME fixes
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@...nel.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.
Powered by blists - more mailing lists