From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: xen-devel <Xen-devel@lists.xenproject.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Update upstream qemu to 2.4.1 for xen-unstable
Date: Fri, 20 Nov 2015 12:36:34 +0100 [thread overview]
Message-ID: <564F05C2.401@m2r.biz> (raw)
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.
next reply other threads:[~2015-11-20 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 11:36 Fabio Fantoni [this message]
2015-11-23 17:37 ` Update upstream qemu to 2.4.1 for xen-unstable Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564F05C2.401@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Xen-devel@lists.xenproject.org \
--cc=anthony.perard@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.