Re: [PATCH 2/2] KVM: arm64: Leave vcpu FPSIMD synchronization in host

2020-07-14 Thread Dave Martin
On Mon, Jul 13, 2020 at 09:42:04PM +0100, Andrew Scull wrote: > On Mon, Jul 13, 2020 at 05:04:21PM +0100, Dave Martin wrote: > > On Fri, Jul 10, 2020 at 10:57:54AM +0100, Andrew Scull wrote: > > > The task state can be checked by the host and the vcpu flags updated > > > before calling into hyp.

Re: [PATCH 2/2] KVM: arm64: Leave vcpu FPSIMD synchronization in host

2020-07-13 Thread Andrew Scull
On Mon, Jul 13, 2020 at 05:04:21PM +0100, Dave Martin wrote: > On Fri, Jul 10, 2020 at 10:57:54AM +0100, Andrew Scull wrote: > > The task state can be checked by the host and the vcpu flags updated > > before calling into hyp. This more neatly separates the concerns and > > removes the need to map

Re: [PATCH 2/2] KVM: arm64: Leave vcpu FPSIMD synchronization in host

2020-07-13 Thread Dave Martin
On Fri, Jul 10, 2020 at 10:57:54AM +0100, Andrew Scull wrote: > The task state can be checked by the host and the vcpu flags updated > before calling into hyp. This more neatly separates the concerns and > removes the need to map the task flags to EL2. > > Hyp acts on the state provided to it by

[PATCH 2/2] KVM: arm64: Leave vcpu FPSIMD synchronization in host

2020-07-10 Thread Andrew Scull
The task state can be checked by the host and the vcpu flags updated before calling into hyp. This more neatly separates the concerns and removes the need to map the task flags to EL2. Hyp acts on the state provided to it by the host and updates it when switching to the vcpu state. No functional