[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 00/35] Migration thread (20121211)
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH 00/35] Migration thread (20121211) |
Date: |
Tue, 11 Dec 2012 15:22:06 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 |
Il 11/12/2012 13:46, Juan Quintela ha scritto:
> Please test & comment & review, Juan.
Please, not this way.
This hardly takes into account all of the comments I sent to this series.
For example on 21 September I wrote about patch 4 that "usleep is broken
under IIRC Solaris (it uses signals and conflicts with qemu-timer.c).
Please use g_usleep instead." It still doesn't do.
At the beginning of November I went through another review of this code.
I found another small problem in patch 4 (it calls migrate_fd_close
twice). I commented that patch 6 has a stale commit message, and
incorrectly uses a global. It still does all of these things.
At the time, I also found that ratelimiting is currently broken
(including in the 1.3 release), and you haven't reviewed my patches to
fix that, nor included them in this series.
You are also ignoring other people's comments too. Peter mentioned on
21 October "Maybe worth adding a comment explaining why we have the two
lists, to save people having to ferret around in the revision history
later?". Nope.
But this is all fine. The worst part is that you *knew* I had worked on
the migration thread code, fixing all the above and more, and redoing
the second half of your series in a way that actually removed the memory
copies and serialized memory contents outside the BQL (no doubt there
are other cleanups that may be in these series and not in mine; I grant
that). Vinod had tested the branch successfully and Orit is already
using it as a base for further improvements.
I was going to ask you today about how to move on with the migration
thread work. Instead I found out that we duplicated effort on fixing
the conflicts, and the review comments have fallen on the floor once more.
So, I'm not going to review this series. I pushed my version of the
patches to github on the migration-thread-20121211 branch. Please
consider at least reviewing it.
Paolo
- [Qemu-devel] [PATCH 21/35] migration: Add buffered_flush error handling, (continued)
- [Qemu-devel] [PATCH 21/35] migration: Add buffered_flush error handling, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 27/35] ram: Use memory_region_test_and_clear_dirty, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 26/35] memory: introduce memory_region_test_and_clear_dirty, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 24/35] ram: rename last_block to last_seen_block, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 35/35] migration: print times for end phase, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 32/35] ram: add free_space parameter to save_live functions, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 30/35] ram: account the amount of transferred ram better, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 29/35] ram: optimize migration bitmap walking, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 31/35] ram: refactor ram_save_block() return value, Juan Quintela, 2012/12/11
- [Qemu-devel] [PATCH 34/35] ram: reuse ram_save_iterate() for the complete stage, Juan Quintela, 2012/12/11
- Re: [Qemu-devel] [PATCH 00/35] Migration thread (20121211),
Paolo Bonzini <=
- [Qemu-devel] [PATCH 33/35] ram: remove xbrle last_stage optimization, Juan Quintela, 2012/12/11