From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio Fantoni Subject: Update upstream qemu to 2.4.1 for xen-unstable Date: Fri, 20 Nov 2015 12:36:34 +0100 Message-ID: <564F05C2.401@m2r.biz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" 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 1ZzjzM-0005Df-TY for Xen-devel@lists.xenproject.org; Fri, 20 Nov 2015 11:36:25 +0000 Received: by wmec201 with SMTP id c201so17344511wme.1 for ; Fri, 20 Nov 2015 03:36:23 -0800 (PST) List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel Cc: Anthony PERARD , Ian Jackson , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org I saw that upstream qemu for xen-unstable is still not updated at least to latest stable version. I tested qemu 2.4.0.1 for some weeks on 2 systems backporting this 2 patches: spice: surface switch fast path requires same format too (I think is good backport it also on future update in xen as it fix a spice regression) xen/HVM: atomically access pointers in bufioreq handling (I suppose that this will be added in xen git too) I also recently tested 2.4.1 (also backporting same 2 patches above) without finding regression for now. Thanks for any reply and sorry for my bad english.