Re: [PATCH] memory: Fix start offset for bitmap log_clear hook

2020-03-02 Thread Paolo Bonzini
On 25/02/20 21:46, Matt Borgerson wrote: > [ ping ] > > Hi Paolo, would you mind taking a quick look at this patch for > memory.c to consider > it for merge? This resolves an issue with dirty bits not being cleared > as expected. > > Here's the Patchwork link: http://patchwork.ozlabs.org/patch/12

Re: [PATCH] memory: Fix start offset for bitmap log_clear hook

2020-02-25 Thread Matt Borgerson
[ ping ] Hi Paolo, would you mind taking a quick look at this patch for memory.c to consider it for merge? This resolves an issue with dirty bits not being cleared as expected. Here's the Patchwork link: http://patchwork.ozlabs.org/patch/1240121/ Thanks for your time! Matt On Tue, Feb 18, 2020

Re: [PATCH] memory: Fix start offset for bitmap log_clear hook

2020-02-18 Thread Peter Xu
On Tue, Feb 18, 2020 at 03:19:10AM -0700, Matt Borgerson wrote: > Currently only the final page offset is being passed to the `log_clear` > hook via `memory_region_clear_dirty_bitmap` after it is used as an > iterator in `cpu_physical_memory_test_and_clear_dirty`. This patch > corrects the start ad

[PATCH] memory: Fix start offset for bitmap log_clear hook

2020-02-18 Thread Matt Borgerson
Currently only the final page offset is being passed to the `log_clear` hook via `memory_region_clear_dirty_bitmap` after it is used as an iterator in `cpu_physical_memory_test_and_clear_dirty`. This patch corrects the start address and size of the region. Signed-off-by: Matt Borgerson --- exec.