Re: [PATCH 01/15] arm64: kvm: Unify users of HVC instruction

2020-05-13 Thread David Brazdil
On Thu, May 07, 2020 at 03:36:33PM +0100, Quentin Perret wrote: > On Thursday 07 May 2020 at 15:01:07 (+0100), Marc Zyngier wrote: > > > /* > > > - * u64 __kvm_call_hyp(void *hypfn, ...); > > > + * u64 __kvm_call_hyp(unsigned long arg, ...); > > > * > > > * This is not really a variadic functi

Re: [PATCH 01/15] arm64: kvm: Unify users of HVC instruction

2020-05-07 Thread Quentin Perret
On Thursday 07 May 2020 at 15:01:07 (+0100), Marc Zyngier wrote: > > /* > > - * u64 __kvm_call_hyp(void *hypfn, ...); > > + * u64 __kvm_call_hyp(unsigned long arg, ...); > > * > > * This is not really a variadic function in the classic C-way and care > > must > > * be taken when calling thi

Re: [PATCH 01/15] arm64: kvm: Unify users of HVC instruction

2020-05-07 Thread Marc Zyngier
On Thu, 30 Apr 2020 15:48:17 +0100, David Brazdil wrote: > > From: Quentin Perret > > Currently, the arm64 KVM code provides __kvm_call_hyp assembly procedure which > does nothing but call the HVC instruction. This is used to call functions by > their pointer in EL2 under nVHE, and abused by __

[PATCH 01/15] arm64: kvm: Unify users of HVC instruction

2020-04-30 Thread David Brazdil
From: Quentin Perret Currently, the arm64 KVM code provides __kvm_call_hyp assembly procedure which does nothing but call the HVC instruction. This is used to call functions by their pointer in EL2 under nVHE, and abused by __cpu_init_hyp_mode to pass a data pointer. The hyp-stub code, on the oth