From: Dave Martin <Dave.Martin@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Edmund Grimley-Evans <edmund.grimley-evans@arm.com>
Subject: Re: [PATCH v2 2/4] arm64/sme: Fix cut'n'paste in ABI document
Date: Thu, 25 Jan 2024 13:49:40 +0000 [thread overview]
Message-ID: <ZbJm9J0QuE6Rx9ba@e133380.arm.com> (raw)
In-Reply-To: <20240124-arm64-sve-sme-doc-v2-2-fe3964fb3c19@kernel.org>
On Wed, Jan 24, 2024 at 06:12:36PM +0000, Mark Brown wrote:
> The ABI for SME is very like that for SVE so bits of the ABI were copied
> but not adequately search and replaced, fix that.
>
> Reported-by: Edmund Grimley-Evans <edmund.grimley-evans@arm.com>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Documentation/arch/arm64/sme.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/arch/arm64/sme.rst b/Documentation/arch/arm64/sme.rst
> index 3d0e53ecac4f..3133d0e91b48 100644
> --- a/Documentation/arch/arm64/sme.rst
> +++ b/Documentation/arch/arm64/sme.rst
> @@ -238,12 +238,12 @@ prctl(PR_SME_SET_VL, unsigned long arg)
> bits of Z0..Z31 except for Z0 bits [127:0] .. Z31 bits [127:0] to become
> unspecified, including both streaming and non-streaming SVE state.
> Calling PR_SME_SET_VL with vl equal to the thread's current vector
> - length, or calling PR_SME_SET_VL with the PR_SVE_SET_VL_ONEXEC flag,
> + length, or calling PR_SME_SET_VL with the PR_SME_SET_VL_ONEXEC flag,
> does not constitute a change to the vector length for this purpose.
>
> * Changing the vector length causes PSTATE.ZA and PSTATE.SM to be cleared.
> Calling PR_SME_SET_VL with vl equal to the thread's current vector
> - length, or calling PR_SME_SET_VL with the PR_SVE_SET_VL_ONEXEC flag,
> + length, or calling PR_SME_SET_VL with the PR_SME_SET_VL_ONEXEC flag,
> does not constitute a change to the vector length for this purpose.
Reviewed-by: Dave Martin <Dave.Martin@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:[~2024-01-25 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 18:12 [PATCH v2 0/4] arm64/fp: Documentation cleanups and clarifications Mark Brown
2024-01-24 18:12 ` [PATCH v2 1/4] arm64/sve: Remove bitrotted comment about syscall behaviour Mark Brown
2024-01-24 18:12 ` [PATCH v2 2/4] arm64/sme: Fix cut'n'paste in ABI document Mark Brown
2024-01-25 13:49 ` Dave Martin [this message]
2024-01-24 18:12 ` [PATCH v2 3/4] arm64/fp: Clarify effect of setting an unsupported system VL Mark Brown
2024-01-25 13:47 ` Dave Martin
2024-01-24 18:12 ` [PATCH v2 4/4] arm64/sme: Remove spurious 'is' in SME documentation Mark Brown
2024-02-21 18:24 ` [PATCH v2 0/4] arm64/fp: Documentation cleanups and clarifications 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=ZbJm9J0QuE6Rx9ba@e133380.arm.com \
--to=dave.martin@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=edmund.grimley-evans@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).