On Fri, 14 Feb 2025 01:57:43 +0000,
Mark Brown <broonie@xxxxxxxxxx> wrote:
>
> I've removed the RFC tag from this version of the series, but the items
> that I'm looking for feedback on remains the same:
>
> - The userspace ABI, in particular:
> - The vector length used for the SVE registers, access to the SVE
> registers and access to ZA and (if available) ZT0 depending on
> the current state of PSTATE.{SM,ZA}.
> - The use of a single finalisation for both SVE and SME.
>
> - The addition of control for enabling fine grained traps in a similar
> manner to FGU but without the UNDEF, I'm not clear if this is desired
> at all and at present this requires symmetric read and write traps like
> FGU. That seemed like it might be desired from an implementation
> point of view but we already have one case where we enable an
> asymmetric trap (for ARM64_WORKAROUND_AMPERE_AC03_CPU_38) and it
> seems generally useful to enable asymmetrically.
>
> This series implements support for SME use in non-protected KVM guests.
[...]
Just to be clear: I do not intend to review a series that doesn't
cover the full gamut of KVM from day 1. Protected mode is an absolute
requirement. It is the largest KVM deployment, and Android phones the
only commonly available platform with SME. If CCA gets merged prior to
SME support, supporting it will also be a requirement.
> Much of this is very similar to SVE, the main additional challenge that
> SME presents is that it introduces a new vector length similar to the
> SVE vector length and two new controls which change the registers seen
> by guests:
>
> - PSTATE.ZA enables the ZA matrix register and, if SME2 is supported,
> the ZT0 LUT register.
> - PSTATE.SM enables streaming mode, a new floating point mode which
> uses the SVE register set with the separately configured SME vector
> length. In streaming mode implementation of the FFR register is
> optional.
>
> It is also permitted to build systems which support SME without SVE, in
> this case when not in streaming mode no SVE registers or instructions
> are available. Further, there is no requirement that there be any
> overlap in the set of vector lengths supported by SVE and SME in a
> system, this is expected to be a common situation in practical systems.
>
> Since there is a new vector length to configure we introduce a new
> feature parallel to the existing SVE one with a new pseudo register for
> the streaming mode vector length. Due to the overlap with SVE caused by
> streaming mode rather than finalising SME as a separate feature we use
> the existing SVE finalisation to also finalise SME, a new define
> KVM_ARM_VCPU_VEC is provided to help make user code clearer. Finalising
> SVE and SME separately would introduce complication with register access
> since finalising SVE makes the SVE regsiters writeable by userspace and
> doing multiple finalisations results in an error being reported.
> Dealing with a state where the SVE registers are writeable due to one of
> SVE or SME being finalised but may have their VL changed by the other
> being finalised seems like needless complexity with minimal practical
> utility, it seems clearer to just express directly that only one
> finalisation can be done in the ABI.
>
> Access to the floating point registers follows the architecture:
>
> - When both SVE and SME are present:
> - If PSTATE.SM == 0 the vector length used for the Z and P registers
> is the SVE vector length.
> - If PSTATE.SM == 1 the vector length used for the Z and P registers
> is the SME vector length.
> - If only SME is present:
> - If PSTATE.SM == 0 the Z and P registers are inaccessible and the
> floating point state accessed via the encodings for the V registers.
> - If PSTATE.SM == 1 the vector length used for the Z and P registers
> - The SME specific ZA and ZT0 registers are only accessible if SVCR.ZA is 1.
>
> The VMM must understand this, in particular when loading state SVCR
> should be configured before other state.
Why SVCR? This isn't a register, just an architected accessor to
PSTATE.{ZA,SM}. Userspace already has direct access to PSTATE, so I
don't understand this requirement.
Isn't it that there is simply a dependency between restoring PSTATE
and any of the vector stuff? Also, how do you preserve the current ABI
that do not have this requirement?
M.
--
Without deviation from the norm, progress is not possible.
