xen: implement pirq type event channels
A privileged PV Xen domain can get direct access to hardware. In order for this to be useful, it must be able to get hardware interrupts. Being a PV Xen domain, all interrupts are delivered as event channels. PIRQ event channels are bound to a pirq number and an interrupt vector. When a IO APIC raises a hardware interrupt on that vector, it is delivered as an event channel, which we can deliver to the appropriate device driver(s). This patch simply implements the infrastructure for dealing with pirq event channels. [ Impact: integrate hardware interrupts into Xen's event scheme ] Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
This commit is contained in:
committed by
Konrad Rzeszutek Wilk
parent
d8e0420603
commit
d46a78b05c
@@ -63,4 +63,15 @@ int xen_set_callback_via(uint64_t via);
|
||||
void xen_evtchn_do_upcall(struct pt_regs *regs);
|
||||
void xen_hvm_evtchn_do_upcall(void);
|
||||
|
||||
/* Allocate an irq for a physical interrupt, given a gsi. "Legacy"
|
||||
* GSIs are identity mapped; others are dynamically allocated as
|
||||
* usual. */
|
||||
int xen_allocate_pirq(unsigned gsi);
|
||||
|
||||
/* Return vector allocated to pirq */
|
||||
int xen_vector_from_irq(unsigned pirq);
|
||||
|
||||
/* Return gsi allocated to pirq */
|
||||
int xen_gsi_from_irq(unsigned pirq);
|
||||
|
||||
#endif /* _XEN_EVENTS_H */
|
||||
|
Reference in New Issue
Block a user