From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen 4.4 development update Date: Tue, 17 Sep 2013 15:55:08 +0100 Message-ID: <52386D4C.3010507@citrix.com> References: <523723B802000078000F3A8E@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VLwgZ-0001qH-9q for xen-devel@lists.xenproject.org; Tue, 17 Sep 2013 14:55:27 +0000 In-Reply-To: <523723B802000078000F3A8E@nat28.tlf.novell.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: Jan Beulich Cc: George Dunlap , xen-devel List-Id: xen-devel@lists.xenproject.org On 16/09/2013 14:28, Jan Beulich wrote: >>>> On 16.09.13 at 15:06, George Dunlap wrote: >> == Open == > * Supposed regression from a3513737 ("x86: allow guest to set/clear > MSI-X mask bit (try 2)"), as per > http://lists.xenproject.org/archives/html/xen-devel/2013-09/msg01589.html. > >> === Clean-ups === > * ACPI WAET table vs RTC emulation mode > > An overly simplified fix was posted a while ago > (http://lists.xenproject.org/archives/html/xen-devel/2013-07/msg00122.html), > but Tim's objection is rather valid. I can't, however, estimate if/when > I would find time to learn what tools side changes are necessary to > accommodate a new HVM param, and hence this is currently stalled. > The current solution (as of 3fa7fb8b ["x86/HVM: RTC code must be > in line with WAET flags passed by hvmloader"]) isn't desirable to be > kept for 4.4. > > Jan Relatedly, there is still an outstanding regression in this code were Win2k3 Enterprise SP2 occasionally falls into an infinite loop probing the RTC. I still need to get to the bottom of why this is happening. ~Andrew