Re: [PATCH 13/20] ARM: KVM: Implement HVC_RESET_VECTORS stub hypercall

2017-02-19 Thread Ard Biesheuvel
On 17 February 2017 at 15:44, Marc Zyngier wrote: > In order to restore HYP mode to its original condition, KVM currently > implements __kvm_hyp_reset(). As we're moving towards a hyp-stub > defined API, it becomes necessary to implement HVC_RESET_VECTORS. > > This patch

Re: [PATCH 13/20] ARM: KVM: Implement HVC_RESET_VECTORS stub hypercall

2017-02-19 Thread Marc Zyngier
On Sun, 19 Feb 2017 08:07:22 + Ard Biesheuvel wrote: > On 17 February 2017 at 15:44, Marc Zyngier wrote: > > In order to restore HYP mode to its original condition, KVM currently > > implements __kvm_hyp_reset(). As we're moving towards a

Re: [PATCH 10/20] ARM: hyp-stub: Use r1 for the soft-restart address

2017-02-19 Thread Marc Zyngier
On Sun, 19 Feb 2017 08:22:23 + Ard Biesheuvel wrote: > On 17 February 2017 at 15:44, Marc Zyngier wrote: > > It is not really obvious why the restart address should be in r3 > > when communicated to the hyp-stub. r1 should be perfectly

Re: [PATCH 10/20] ARM: hyp-stub: Use r1 for the soft-restart address

2017-02-19 Thread Ard Biesheuvel
On 17 February 2017 at 15:44, Marc Zyngier wrote: > It is not really obvious why the restart address should be in r3 > when communicated to the hyp-stub. r1 should be perfectly adequate, > and consistent with the rest of the code. > > Signed-off-by: Marc Zyngier

Re: [PATCH 13/20] ARM: KVM: Implement HVC_RESET_VECTORS stub hypercall

2017-02-19 Thread Ard Biesheuvel
On 17 February 2017 at 15:44, Marc Zyngier wrote: > In order to restore HYP mode to its original condition, KVM currently > implements __kvm_hyp_reset(). As we're moving towards a hyp-stub > defined API, it becomes necessary to implement HVC_RESET_VECTORS. > > This patch