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 3/4] arm64/fp: Clarify effect of setting an unsupported system VL
Date: Tue, 23 Jan 2024 15:49:27 +0000 [thread overview]
Message-ID: <Za/gB3oCNAyiPPnu@e133380.arm.com> (raw)
In-Reply-To: <20240122-arm64-sve-sme-doc-v1-3-3d492e45265b@kernel.org>
On Mon, Jan 22, 2024 at 08:41:53PM +0000, Mark Brown wrote:
> The documentation for system vector length configuration does not cover all
> cases where unsupported values are written, tighten it up.
>
> Reported-by: Edmund Grimley-Evans <edmund.grimley-evans@arm.com>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Documentation/arch/arm64/sme.rst | 5 ++---
> Documentation/arch/arm64/sve.rst | 5 ++---
> 2 files changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/arch/arm64/sme.rst b/Documentation/arch/arm64/sme.rst
> index 3133d0e91b48..ba0a5e5b2523 100644
> --- a/Documentation/arch/arm64/sme.rst
> +++ b/Documentation/arch/arm64/sme.rst
> @@ -379,9 +379,8 @@ The regset data starts with struct user_za_header, containing:
> /proc/sys/abi/sme_default_vector_length
>
> Writing the text representation of an integer to this file sets the system
> - default vector length to the specified value, unless the value is greater
> - than the maximum vector length supported by the system in which case the
> - default vector length is set to that maximum.
> + default vector length to the specified value rounded to a supported value
> + using the same rules as for setting vector length via prctl().
Do parallel changes need to be made in sve.rst?
(There seems to be so much duplication and copy-paste between these
files that I wonder whether it would make sense to merge them... but
that's probably a separate discussion.)
Nit: is it better to name the prctl here than just to say prctl()?
That would be easier for the reader to cross-reference.
>
> The result can be determined by reopening the file and reading its
> contents.
> diff --git a/Documentation/arch/arm64/sve.rst b/Documentation/arch/arm64/sve.rst
> index b45a2da19bf1..b923727ff4b9 100644
> --- a/Documentation/arch/arm64/sve.rst
> +++ b/Documentation/arch/arm64/sve.rst
> @@ -423,9 +423,8 @@ The regset data starts with struct user_sve_header, containing:
> /proc/sys/abi/sve_default_vector_length
>
> Writing the text representation of an integer to this file sets the system
> - default vector length to the specified value, unless the value is greater
> - than the maximum vector length supported by the system in which case the
> - default vector length is set to that maximum.
> + default vector length to the specified value rounded to a supported value
> + using the same rules as for setting vector length via prctl().
Ditto.
[...]
Cheers
---Dave
next prev parent reply other threads:[~2024-01-23 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 20:41 [PATCH 0/4] arm64/fp: Documentation cleanups and clarifications Mark Brown
2024-01-22 20:41 ` [PATCH 1/4] arm64/sve: Remove bitrotted comment about syscall behaviour Mark Brown
2024-01-23 15:44 ` Dave Martin
2024-01-23 17:31 ` Mark Brown
2024-01-23 17:54 ` Dave Martin
2024-01-23 18:11 ` Mark Brown
2024-01-24 14:04 ` Dave Martin
2024-01-22 20:41 ` [PATCH 2/4] arm64/sme: Fix cut'n'paste in ABI document Mark Brown
2024-01-22 20:41 ` [PATCH 3/4] arm64/fp: Clarify effect of setting an unsupported system VL Mark Brown
2024-01-23 15:49 ` Dave Martin [this message]
2024-01-23 18:42 ` Mark Brown
2024-01-24 14:09 ` Dave Martin
2024-01-22 20:41 ` [PATCH 4/4] arm64/sme: Remove spurious 'is' in SME documentation Mark Brown
2024-01-23 15:50 ` Dave Martin
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=Za/gB3oCNAyiPPnu@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