WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH] x86: change IO-APIC ack method default forsingle

To: Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] x86: change IO-APIC ack method default forsingle IO-APIC systems
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Wed, 21 Jan 2009 22:35:54 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 21 Jan 2009 06:37:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49774067.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <49773D8A.76E4.0078.0@xxxxxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401C609FB38@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49774067.76E4.0078.0@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acl71T//HX7hj5z9SG+/YP4+V8s2WAAABd0Q
Thread-topic: [Xen-devel] [PATCH] x86: change IO-APIC ack method default forsingle IO-APIC systems
Jan Beulich <mailto:jbeulich@xxxxxxxxxx> wrote:
>>>> "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> 21.01.09 15:23 >>>
>>> 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
>> 
>> This is a bit strange, a bit curios that do you know the reason that it
>> not working? 
> 
> I too find it strange (otherwise I wouldn't have decided to
> drop that patch),
> but given that it always worked before, we have a solution at
> hand, and I
> don't have an affected machine available for debugging, I
> wanted to save
> myself and the reporter trying to figure out what's going on there from
> remote. 

Got it. Just want to make sure it is still under debug otherwise it may bite us 
in future :-)

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