From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen 4.4 development update: Feature freeze has started Date: Fri, 15 Nov 2013 14:52:16 +0000 Message-ID: <52863520.40901@citrix.com> References: <528114C6.8080505@citrix.com> <5286316E.9070609@eu.citrix.com> <52863441.1080907@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <52863441.1080907@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 15/11/13 14:48, Andrew Cooper wrote: > On 15/11/13 14:36, George Dunlap wrote: >> On 11/11/13 17:32, Andrew Cooper wrote: >>> * HPET interrupt stack overflow (when using hpet_broadcast mode and MSI >>> capable HPETs) >>> status: patches posted, undergoing review iteration. >> Is this a bug? >> >> -George > Yes - it causes a double fault in debug builds of Xen. > > In non-debug builds, Xen will survive, but the underlying cause is that > interrupts can erroneously stack with lower priority on top of higher > priority. > > The patches have been Reviewed-by Tim, and are currently in XenServer > trunk having a good trashing across all our hardware. I actually meant "thrashing" here. ("trashing" was v3 which had a bug on Nehalem/Westmere boxes which broke 1/3rd of our test lab. XenRT was very unhappy with me for that) ~Andrew