From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Fuad Tabba <tabba@google.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev
Subject: Re: [PATCH v2 2/4] arm64/fpsimd: Discover maximum vector length implemented by any CPU
Date: Thu, 4 Jul 2024 15:18:56 +0100 [thread overview]
Message-ID: <ZoavUGcYLULHpVfg@arm.com> (raw)
In-Reply-To: <20240606-kvm-arm64-fix-pkvm-sve-vl-v2-2-c88f4eb4b14b@kernel.org>
On Thu, Jun 06, 2024 at 04:21:44PM +0100, Mark Brown wrote:
> When discovering the vector lengths for SVE and SME we do not currently
> record the maximum VL supported on any individual CPU. This is expected
> to be the same for all CPUs but the architecture allows asymmetry, if we
> do encounter an asymmetric system then some CPUs may support VLs higher
> than the maximum Linux will use. Since the pKVM hypervisor needs to
> support saving and restoring anything the host can physically set it
> needs to know the maximum value any CPU could have, add support for
> enumerating it and validation for late CPUs.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
I guess the %lu suggested by Fuad can be done when applying the patch.
next prev parent reply other threads:[~2024-07-04 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 15:21 [PATCH v2 0/4] KVM: arm64: Fix underallocation of storage for SVE state Mark Brown
2024-06-06 15:21 ` Mark Brown
2024-06-06 15:21 ` [PATCH v2 1/4] arm64/fpsimd: Introduce __bit_to_vl() helper Mark Brown
2024-06-06 15:21 ` Mark Brown
2024-07-04 14:17 ` Catalin Marinas
2024-06-06 15:21 ` [PATCH v2 2/4] arm64/fpsimd: Discover maximum vector length implemented by any CPU Mark Brown
2024-06-06 15:21 ` Mark Brown
2024-06-07 7:33 ` Fuad Tabba
2024-06-07 7:33 ` Fuad Tabba
2024-07-04 14:18 ` Catalin Marinas [this message]
2024-07-04 15:12 ` Mark Brown
2024-06-06 15:21 ` [PATCH v2 3/4] KVM: arm64: Fix FFR offset calculation for pKVM host state save and restore Mark Brown
2024-06-06 15:21 ` Mark Brown
2024-06-06 15:21 ` [PATCH v2 4/4] KVM: arm64: Avoid underallocating storage for host SVE state Mark Brown
2024-06-06 15:21 ` Mark Brown
2024-07-04 14:20 ` [PATCH v2 0/4] KVM: arm64: Fix underallocation of storage for " 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=ZoavUGcYLULHpVfg@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--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 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.