Re: [PATCH v6 3/4] x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for ACRN guest upcall vector

On Mon, May 27, 2019 at 10:21:20AM +0800, Zhao, Yakui wrote: > Very sorry that this issue is not triggered as the used .config in my test > doesn't enable the check of "-Werror=implict-function-declaration". It is more like, you're not building this particular .config. -- Regards/Gruss,

Re: [PATCH v6 3/4] x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for ACRN guest upcall vector

On 2019年05月16日 01:23, Borislav Petkov wrote: On Tue, Apr 30, 2019 at 11:45:25AM +0800, Zhao Yakui wrote: @@ -30,6 +36,29 @@ static bool acrn_x2apic_available(void) return false; } +static void (*acrn_intr_handler)(void); + +__visible void __irq_entry

Re: [PATCH v6 3/4] x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for ACRN guest upcall vector

On Tue, Apr 30, 2019 at 11:45:25AM +0800, Zhao Yakui wrote: > @@ -30,6 +36,29 @@ static bool acrn_x2apic_available(void) > return false; > } > > +static void (*acrn_intr_handler)(void); > + > +__visible void __irq_entry acrn_hv_vector_handler(struct pt_regs *regs) > +{ > + struct

[PATCH v6 3/4] x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for ACRN guest upcall vector

Linux kernel uses the HYPERVISOR_CALLBACK_VECTOR for hypervisor upcall vector. It is already used for Xen and HyperV. After the ACRN hypervisor is detected, it will also use this defined vector to notify the ACRN guest. Co-developed-by: Jason Chen CJ Signed-off-by: Jason Chen CJ Signed-off-by: