On 01/19/2018 07:27 PM, Philippe Mathieu-Daudé wrote:
On 01/15/2018 01:14 PM, Peter Maydell wrote:
On 15 January 2018 at 11:52, Juan Quintela <quint...@redhat.com> wrote:
Hi
- rebase on top of lastest
- fix compilation on 32bit machines
- add Peter Xu cleanups
Please, apply.
The following changes since commit fd06527b80c88c8dde1b35fdc692685b68d2fd93:
Merge remote-tracking branch 'remotes/thibault/tags/samuel-thibault' into
staging (2018-01-15 10:39:29 +0000)
are available in the Git repository at:
git://github.com/juanquintela/qemu.git tags/migration/20180115
for you to fetch changes up to 816306826a45f4d15352e32d157172af3a35899f:
migration: remove notify in fd_error (2018-01-15 12:48:13 +0100)
----------------------------------------------------------------
migration/next for 20180115
Applied, thanks.
We have armel/armhf/powerpc hosts failing since this pull due to commit
3be98be4e9f.
Those target are currently tested on Shippable CI, eventually adding an
IRC bot we could notice.
I know companies using QEMU system in embedded armel/armhf hosts, I
don't know about the ppc32 hosts.
This is however unlikely the migration features are used there.
If 64bit atomic op are required for migration (performance/security) but
not on 32bit system, one way to fix it could be to have the migration
code being optional... so we can disable it on 32bit hosts.
Regards,
Phil.
Thank you Phil for report,
I have a release this week and it's not yet over.
As I remember, I tested build in QEMU's docker build system,
but now I checked it on i386 Ubuntu, and yes linker says about unresolved
atomic symbols. Next week, I'll have a time to investigate it deeper.
--
Best regards,
Alexey Perevalov
