Hi Dave, On 18/02/2019 19:52, Dave Martin wrote:
The current FPSIMD/SVE context handling support for non-task (i.e., KVM vcpu) contexts does not take SVE into account. This means that
NIT: Double-space before "This".
only task contexts can safely use SVE at present. In preparation for enabling KVM guests to use SVE, it is necessary to keep track of SVE state for non-task contexts too. This patch adds the necessary support, removing assumptions from the context switch code about the location of the SVE context storage. When binding a vcpu context, its vector length is arbitrarily specified as SVE_VL_MIN for now. In any case, because TIF_SVE is
NIT: Double-space before "In".
presently cleared at vcpu context bind time, the specified vector length will not be used for anything yet. In later patches TIF_SVE
NIT: Double-space before "In".
will be set here as appropriate, and the appropriate maximum vector length for the vcpu will be passed when binding.
Cheers, -- Julien Grall _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
