From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] arm64/sve: Thin out initialisation sanity-checks for sve_max_vl
Date: Thu, 24 May 2018 11:40:55 +0100 [thread overview]
Message-ID: <20180524104053.GB28425@arm.com> (raw)
In-Reply-To: <1527097616-25214-2-git-send-email-Dave.Martin@arm.com>
On Wed, May 23, 2018 at 06:46:55PM +0100, Dave Martin wrote:
> Now that the kernel SVE support is reasonably mature, it is
> excessive to default sve_max_vl to the invalid value -1 and then
> sprinkle WARN_ON()s around the place to make sure it has been
> initialised before use. The cpufeatures code already runs pretty
> early, and will ensure sve_max_vl gets initialised.
>
> This patch initialises sve_max_vl to something sane that will be
> supported by every SVE implementation, and removes most of the
> sanity checks.
>
> The checks in find_supported_vector_length() are retained for now.
> If anything goes horribly wrong, we are likely to trip a check here
> sooner or later.
>
> Signed-off-by: Dave Martin <Dave.Martin@arm.com>
> ---
> arch/arm64/kernel/fpsimd.c | 17 ++++-------------
> arch/arm64/kernel/ptrace.c | 3 ---
> 2 files changed, 4 insertions(+), 16 deletions(-)
Thanks, this makes the code a bit more readable imo:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2018-05-24 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 17:46 [PATCH v4 0/2] arm64: signal: Report signal frame size to userspace via auxv Dave Martin
2018-05-23 17:46 ` [PATCH v4 1/2] arm64/sve: Thin out initialisation sanity-checks for sve_max_vl Dave Martin
2018-05-24 10:40 ` Will Deacon [this message]
2018-05-23 17:46 ` [PATCH v4 2/2] arm64: signal: Report signal frame size to userspace via auxv Dave Martin
2018-05-24 12:49 ` Will Deacon
2018-05-24 15:55 ` Dave Martin
2018-05-24 16:50 ` Will Deacon
2018-05-24 17:07 ` Dave Martin
2018-05-25 11:32 ` Will Deacon
2018-05-25 14:39 ` 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=20180524104053.GB28425@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.