[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86: change IO-APIC ack method default for single IO-APIC systems


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Wed, 21 Jan 2009 14:35:54 +0000
  • Cc:
  • Delivery-date: Wed, 21 Jan 2009 06:36:19 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acl71ZCKR5afz5isfE6vv8IHSNIdTg==
  • Thread-topic: [Xen-devel] [PATCH] x86: change IO-APIC ack method default for single IO-APIC systems

On 21/01/2009 14:21, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> "ioapic_ack=old". With that knowledge I think it is now reasonable to
> include that patch in -unstable, as the introduction of the 'new' ack
> method was only to address issues with certain chipsets silently
> setting up alternative IRQ routes when RTEs in secondary IO-APICs got
> masked.

I don't specifically recall that this issue required two IO-APICs. In fact I
think it did not. It was actually something to do with the chipset trying to
distinguish between an OS using 'legacy' routing versus 'mp-bios' routing,
via a rather distasteful IO-APIC hack. Unfortunately the hack was not that
uncommon and I don't think those chipsets had more than one IO-APIC.

Overall I think ack_type new has worked quite well. I was actually about to
remove the old ack_type! (But now I won't ;-) I'm not inclined to take this
patch though.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.