From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: 4.4.2-rc2 and 4.3.4-rc2 have been tagged Date: Tue, 3 Mar 2015 18:13:31 +0000 Message-ID: <54F5F9CB.90807@citrix.com> References: <54F5FAF50200007800065E05@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YSrK4-0006Lj-44 for xen-devel@lists.xenproject.org; Tue, 03 Mar 2015 18:13:36 +0000 In-Reply-To: <54F5FAF50200007800065E05@mail.emea.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 , xen-devel List-Id: xen-devel@lists.xenproject.org On 03/03/15 17:18, Jan Beulich wrote: > All, > > aiming at releases with, as before, presumably no further RC on both > of the branches (even more so with the long delay already incurred), > please test! (The plan however is to incorporate the fixes for the XSAs > that are going to go public during the next several days; unless > something extremely important shows up, the expectation is for no > other changes to go in before the release.) > > To remind you, 4.3.4 is expected to be the last xen.org coordinated > release on the 4.3 series. > > Thanks, Jan My NMI shootdown fixes still suffer from the TLB shootdown issue which you identified. I notice your patch is still not even in staging (lacking acks?) but it has been thoroughly tested by XenServer. If that patch can't be fasttracked through, it might be worth introducing an extra fixmap entry in older trees to avoid introducing a regression into the crash path for systems using tboot. ~Andrew