search for: disable_pirq

...reable = 0; char *name; + irq = xen_irq_from_gsi(gsi); + if (irq > 0) + return irq; + if (set_pirq) pirq = gsi; diff --git a/drivers/xen/events.c b/drivers/xen/events.c index 0a8a17c..6908e4c 100644 --- a/drivers/xen/events.c +++ b/drivers/xen/events.c @@ -611,7 +611,7 @@ static void disable_pirq(struct irq_data *data) disable_dynirq(data); } -static int find_irq_by_gsi(unsigned gsi) +int xen_irq_from_gsi(unsigned gsi) { struct irq_info *info; @@ -625,6 +625,7 @@ static int find_irq_by_gsi(unsigned gsi) return -1; } +EXPORT_SYMBOL_GPL(xen_irq_from_gsi); /* * Do not make...

...mer_interrupt+0x28/0xfc [354047.224054] [<ffffffff81244771>] ? get_cycles+0x5/0x8 [354047.224054] [<ffffffff8124561e>] ? add_interrupt_randomness+0x38/0x155 [354047.224054] [<ffffffff8109124d>] ? handle_irq_event_percpu+0x50/0x17d [354047.224054] [<ffffffff8121ca3a>] ? disable_pirq+0x2/0x2 [354047.224054] [<ffffffff8121c624>] ? info_for_irq+0x7/0x17 [354047.224054] [<ffffffff81093847>] ? handle_percpu_irq+0x3a/0x4f [354047.224054] [<ffffffff8121c866>] ? __xen_evtchn_do_upcall+0xd3/0x287 [354047.224054] [<ffffffff8104b780>] ? __local_bh_enable+0x40...

...354047.224054] [<ffffffff81244771>] ? get_cycles+0x5/0x8 > [354047.224054] [<ffffffff8124561e>] ? > add_interrupt_randomness+0x38/0x155 > [354047.224054] [<ffffffff8109124d>] ? > handle_irq_event_percpu+0x50/0x17d > [354047.224054] [<ffffffff8121ca3a>] ? disable_pirq+0x2/0x2 > [354047.224054] [<ffffffff8121c624>] ? info_for_irq+0x7/0x17 > [354047.224054] [<ffffffff81093847>] ? handle_percpu_irq+0x3a/0x4f > [354047.224054] [<ffffffff8121c866>] ? > __xen_evtchn_do_upcall+0xd3/0x287 > [354047.224054] [<ffffffff8104b780>]...

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths