Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Catalin Marinas <catalin.marinas@arm.com>
To:     Will Deacon <will@kernel.org>, Mark Brown <broonie@kernel.org>
Cc:     Mark Rutland <mark.rutland@arm.com>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/sme: Optimise SME exit on syscall entry
Date:   Thu, 12 Jan 2023 17:49:34 +0000
Message-Id: <167354575614.3644139.13835865624687417471.b4-ty@arm.com>
In-Reply-To: <20230110-arm64-sme-syscall-smstop-v1-1-ac94235fd810@kernel.org>
References: <20230110-arm64-sme-syscall-smstop-v1-1-ac94235fd810@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 10 Jan 2023 19:34:36 +0000, Mark Brown wrote:
> Our ABI says that we exit streaming mode on syscall entry. Currently we
> check if we are in streaming mode before doing this but since we have a
> SMSTOP SM instruction which will clear SVCR.SM in a single atomic operation
> we can save ourselves the read of the system register and check of the flag
> and just unconditionally do the SMSTOP SM. If we are not in streaming mode
> it results in a noop change to SVCR, if we are in streaming mode we will
> exit as desired.
> 
> [...]

Applied to arm64 (for-next/sme), thanks!

[1/1] arm64/sme: Optimise SME exit on syscall entry
      https://git.kernel.org/arm64/c/b2482807fbd4

-- 
Catalin