[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: 4.0/4.1 requests - IO-APIC EOI [RFC]
On 08/09/11 14:40, Jan Beulich wrote: >>>> On 08.09.11 at 15:18, Andrew Cooper <andrew.cooper3@xxxxxxxxxx> wrote: >> --- SNIP --- >> >> Attached is my first attempt at expanding the EOI to work on older >> IO-APICs. It has not undergone any significant testing yet. >> >> Does this look suitable? > It looks correct, but I'd prefer not having two io_apic_eoi_*() functions: > Namely in the "normal" __eoi_IO_APIC_irq() case you have pin *and* > vector readily available, and hence there is no need to look up anything. > So perhaps a better option would be to pass both pin and vector to > io_apic_eoi() (using e.g. -1 to identify the "unknown-needs-lookup" > case). > > Jan Ok - I will refactor with that suggestion. Also, the code in end_level_ioapic_irq() suggests masking the entry while playing with it, so I will include that as well. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |