search for: assign_irq_vector

Displaying 20 results from an estimated 35 matches for "assign_irq_vector".

2011 Nov 08
2
[PATCH] x86/IRQ: create_irq() should call assign_irq_vector()
... rather than __assign_irq_vector(), to ensure desc->affinity gets initialized properly. This at once eliminates the need to forward-declare the latter function. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/irq.c +++ b/xen/arch/x86/irq.c @@ -25,7 +25,6 @@ #include <public/physdev.h> static...
2007 Aug 30
4
free_irq_vector on ia64
Hi Alex: I was looking at an ia64 bug report and noticed that we don''t actually free IRQs in the free_irq_vector hypercall. This would eventually lead to alloc_irq_vector failing. Unless I''m mistaken something like calling pci_disable_device and pci_enable_device can lead to this situation. So I''m wondering what the original problem was and how could we resolve it
2008 Oct 08
0
[PATCH] Patches to free MSI vector when pirq unmapped
...arch/x86/irq.c, since that should be part of irq managment, no logic changes. The second patch(msi_vector_clean.patch) free the vector when the pirq is unmapped or when domain destroy. One thing need notice for this patch is, current code will not assign FIRST_DYNAMIC_VECTOR in the first round of assign_irq_vector since the current_vector is added immediately, I didn''t try to fix it, since now it can be allocated in the second round. The third patch (msi_vector_linux.patch) apply to linux hg tree, it fix one issue on msi-xen.c. Signed-off-by: Jiang, Yunhong <yunhong.jiang@intel.com> Thanks...
2008 Apr 30
16
[PATCH 00/15] ia64/pv_ops take 5
Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Now all the comments so far have been addressed, but only a few exceptions. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops.
2008 Apr 30
16
[PATCH 00/15] ia64/pv_ops take 5
Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Now all the comments so far have been addressed, but only a few exceptions. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops.
2008 Feb 21
28
[PATCH 00/28] ia64/xen domU paravirtualization
Hi linux/ia64 developers. Few days before Eddie posted the mail for Linux/IA64 paravirtualization. But only a few responded partially because there was no reviewable patches. Here is the patches for xen/ia64 Linux paravirtualization. The goal is to merge IA64 xen Linux paravirtualization for both domU and dom0 eventually. However the first step is to merge domU portion. As you can see from the
2008 Apr 09
15
[PATCH 00/15] RFC: ia64/pv_ops take 4
Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Please review and comments. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops. Currently only ia64/xen pv_ops implementation
2008 Apr 09
15
[PATCH 00/15] RFC: ia64/pv_ops take 4
Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Please review and comments. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops. Currently only ia64/xen pv_ops implementation
2008 May 19
18
[PATCH 00/17] ia64/pv_ops take 6
Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops
2008 May 19
18
[PATCH 00/17] ia64/pv_ops take 6
Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops
2003 Dec 01
0
No subject
...speed is 132.4526 MHz. Error: only one processor found. enabling symmetric IO mode... ...done. ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 1 ...changing IO-APIC physical APIC ID to 2 init IO_APIC IRQs IO-APIC (apicid-pin) 1-0, 1-2, 1-5, 1-10, 1-13, 2-10, 2-11, 2-12, 2-13WARNING: ASSIGN_IRQ_VECTOR wrapped back to 52 not connected. ...trying to set up timer as ExtINT... .. (found pin 0) ... works. number of MP IRQ sources: 30. number of IO-APIC #1 registers: 16. number of IO-APIC #2 registers: 16. testing the IO APIC....................... IO APIC #1...... .... register #00: 01000000 .........
2011 Mar 09
0
[PATCH 04/11] x86: cleanup mpparse.c
...k) extern const struct genapic *genapic; +extern const struct genapic apic_default; const cpumask_t *target_cpus_all(void); --- 2011-03-09.orig/xen/include/asm-x86/io_apic.h +++ 2011-03-09/xen/include/asm-x86/io_apic.h @@ -212,4 +212,6 @@ static inline void ioapic_resume(void) { extern int assign_irq_vector(int irq); extern int free_irq_vector(int vector); +unsigned highest_gsi(void); + #endif --- 2011-03-09.orig/xen/include/asm-x86/mach-generic/mach_apic.h +++ 2011-03-09/xen/include/asm-x86/mach-generic/mach_apic.h @@ -28,8 +28,7 @@ static inline void enable_apic_mode(void extern u32 bios_cpu_...
2007 May 15
3
[PATCH 1/12] Add suspend/resume to devices owned by Xen
..._renumber_irq)(int ioapic, int irq); +extern int ioapic_suspend(void); +extern int ioapic_resume(void); #else /* !CONFIG_X86_IO_APIC */ #define io_apic_assign_pci_irqs 0 +static inline int ioapic_suspend(void) {return 0}; +static inline int ioapic_resume(void) {return 0}; #endif extern int assign_irq_vector(int irq); diff -r 3ef0510e44d0 xen/include/asm-x86/irq.h --- a/xen/include/asm-x86/irq.h Tue May 08 10:21:23 2007 +0100 +++ b/xen/include/asm-x86/irq.h Mon May 14 15:05:28 2007 -0400 @@ -35,6 +35,8 @@ void enable_8259A_irq(unsigned int irq); void enable_8259A_irq(unsigned int irq); int i8259A_irq...
2008 Sep 26
2
RE: [Xen-changelog] [xen-unstable] x86: Properly synchronise updates to pirq-to-vector mapping.
...p(int cmd, XEN_GUEST_H case PHYSDEVOP_alloc_irq_vector: { struct physdev_irq irq_op; - unsigned long flags; ret = -EFAULT; if ( copy_from_guest(&irq_op, arg, 1) != 0 ) @@ -437,9 +441,9 @@ ret_t do_physdev_op(int cmd, XEN_GUEST_H irq_op.vector = assign_irq_vector(irq); - spin_lock_irqsave(&dom0->arch.irq_lock, flags); + spin_lock(&dom0->evtchn_lock); ret = map_domain_pirq(dom0, irq_op.irq, irq_op.vector, NULL); - spin_unlock_irqrestore(&dom0->arch.irq_lock, flags); + spin_unlock(&dom0->evtchn...
2008 Sep 23
9
Xen crash on dom0 shutdown
There is a BUG_ON() at xen/arch/x86/physdev.c:169 which appears to be dependent upon guest behavior (should close event channel before un-mapping pirq), rather than on internal hypervisor state. In 2.6.18, this likely goes unnoticed because pci_device_shutdown() only calls all the driver shutdown routines. In newer kernels, however, it also calls pci_msi_shutdown() and pci_msix_shutdown(), which
2007 Apr 18
2
refactoring io_apic.c
...ely only the timer IRQ - * is so screwy. Thanks to Brian Perkins for testing/hacking this beast - * fanatically on his truly buggy board. - */ -static inline void check_timer(void) -{ - int pin1, pin2; - int vector; - - /* - * get/set the timer IRQ vector: - */ - disable_8259A_irq(0); - vector = assign_irq_vector(0); - set_intr_gate(vector, interrupt[0]); - - /* - * Subtle, code in do_timer_interrupt() expects an AEOI - * mode for the 8259A whenever interrupts are routed - * through I/O APICs. Also IRQ0 has to be enabled in - * the 8259A which implies the virtual wire has to be - * disabled in the loc...
2007 Apr 18
2
refactoring io_apic.c
...ely only the timer IRQ - * is so screwy. Thanks to Brian Perkins for testing/hacking this beast - * fanatically on his truly buggy board. - */ -static inline void check_timer(void) -{ - int pin1, pin2; - int vector; - - /* - * get/set the timer IRQ vector: - */ - disable_8259A_irq(0); - vector = assign_irq_vector(0); - set_intr_gate(vector, interrupt[0]); - - /* - * Subtle, code in do_timer_interrupt() expects an AEOI - * mode for the 8259A whenever interrupts are routed - * through I/O APICs. Also IRQ0 has to be enabled in - * the 8259A which implies the virtual wire has to be - * disabled in the loc...
2008 Mar 05
51
[PATCH 00/50] ia64/xen take 3: ia64/xen domU paravirtualization
Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it
2008 Mar 05
51
[PATCH 00/50] ia64/xen take 3: ia64/xen domU paravirtualization
Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it
2008 Apr 30
23
[PATCH 00/23] ia64/xen domU take 5
Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to