mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-26 10:25:06 +07:00
4a5b69464e
Currently, the event channel rebind code is gated with the presence of the vector callback. The virtual interrupt controller on ARM has the concept of per-CPU interrupt (PPI) which allow us to support per-VCPU event channel. Therefore there is no need of vector callback for ARM. Xen is already using a free PPI to notify the guest VCPU of an event. Furthermore, the xen code initialization in Linux (see arch/arm/xen/enlighten.c) is requesting correctly a per-CPU IRQ. Introduce new helper xen_support_evtchn_rebind to allow architecture decide whether rebind an event is support or not. It will always return true on ARM and keep the same behavior on x86. This is also allow us to drop the usage of xen_have_vector_callback entirely in the ARM code. Signed-off-by: Julien Grall <julien.grall@citrix.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
35 lines
767 B
C
35 lines
767 B
C
#ifndef _ASM_X86_XEN_EVENTS_H
|
|
#define _ASM_X86_XEN_EVENTS_H
|
|
|
|
enum ipi_vector {
|
|
XEN_RESCHEDULE_VECTOR,
|
|
XEN_CALL_FUNCTION_VECTOR,
|
|
XEN_CALL_FUNCTION_SINGLE_VECTOR,
|
|
XEN_SPIN_UNLOCK_VECTOR,
|
|
XEN_IRQ_WORK_VECTOR,
|
|
XEN_NMI_VECTOR,
|
|
|
|
XEN_NR_IPIS,
|
|
};
|
|
|
|
static inline int xen_irqs_disabled(struct pt_regs *regs)
|
|
{
|
|
return raw_irqs_disabled_flags(regs->flags);
|
|
}
|
|
|
|
/* No need for a barrier -- XCHG is a barrier on x86. */
|
|
#define xchg_xen_ulong(ptr, val) xchg((ptr), (val))
|
|
|
|
extern int xen_have_vector_callback;
|
|
|
|
/*
|
|
* Events delivered via platform PCI interrupts are always
|
|
* routed to vcpu 0 and hence cannot be rebound.
|
|
*/
|
|
static inline bool xen_support_evtchn_rebind(void)
|
|
{
|
|
return (!xen_hvm_domain() || xen_have_vector_callback);
|
|
}
|
|
|
|
#endif /* _ASM_X86_XEN_EVENTS_H */
|