v3:
- dropping patch 1 because I'm going to drop the has_coalesced_ranges
variable later...
- moving previous patch 2 as patch 1 because I think it's definitely
solving a standalone issue of KVM, and also it'll introduce a helper
function that will be used in follow up patches.
- added new patches
- patch 3: a cleanup and prepares for the next
- patch 4: fixes another issue when add/clear coalescing ranges that
Paolo pointed out
v2:
- simply migrate has_coalesced_range in patch 1, while I added
comments in the code because that can be a bit unobvious [Paolo]
v1 is here:
https://lists.gnu.org/archive/html/qemu-devel/2019-08/msg03293.html
Peter Xu (4):
memory: Split zones when do coalesced_io_del()
memory: Remove has_coalesced_range counter
memory: Refactor memory_region_clear_coalescing
memory: Fix up memory_region_{add|del}_coalescing
memory.c | 99 +++++++++++++++++++++++++++++---------------------------
1 file changed, 52 insertions(+), 47 deletions(-)
--
2.21.0
