From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH] x86: change IO-APIC ack method default forsingle IO-APIC systems Date: Wed, 21 Jan 2009 14:44:54 +0000 Message-ID: <497742F6.76E4.0078.0@novell.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Yunhong Jiang , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org >>> Keir Fraser 21.01.09 15:37 >>> >On 21/01/2009 14:23, "Jiang, Yunhong" wrote: > >> xen-devel-bounces@lists.xensource.com <> wrote: >>> Ever since 3.0.2 we've been carrying this patch in our products. Since >>> there was no indication that there would be anything wrong with the >>> 'new' IO-APIC ack method added back then, we finally decided to drop >>> this patch recently from SLE11, to find that the subsequent release >>> candidate failed to work on at least on system without using >>=20 >> This is a bit strange, a bit curios that do you know the reason that it = not >> working?=20 > >Yes - this also -- there doesn't seem to be a good reason that the 'new' >ack_type wouldn't work in all cases. We're also somewhat depending on it = (or >similar) for unmaskable MSIs. Right - but MSIs were the only interrupts staying alive on that system = with the 'new' method. Jan