On Thu, Feb 01, 2024, Shaoqin Huang wrote:
> > > /*
> > >* We reserve page table for 2 times of extra dirty mem which
> > >* will definitely cover the original (1G+) test range. Here
> > > @@ -825,6 +832,13 @@ static void run_test(enum vm_guest_mode mode, void
>
Hi Sean,
Thanks for your reviewing.
On 1/27/24 04:25, Sean Christopherson wrote:
+Peter
On Fri, Nov 17, 2023, Shaoqin Huang wrote:
When execute the dirty_log_test on some aarch64 machine, it sometimes
trigger the ASSERT:
Test Assertion Failure
dirty_log_test.c:384: dirty_ring_vc
+Peter
On Fri, Nov 17, 2023, Shaoqin Huang wrote:
> When execute the dirty_log_test on some aarch64 machine, it sometimes
> trigger the ASSERT:
>
> Test Assertion Failure
> dirty_log_test.c:384: dirty_ring_vcpu_ring_full
> pid=14854 tid=14854 errno=22 - Invalid argument
> 1 0x
When execute the dirty_log_test on some aarch64 machine, it sometimes
trigger the ASSERT:
Test Assertion Failure
dirty_log_test.c:384: dirty_ring_vcpu_ring_full
pid=14854 tid=14854 errno=22 - Invalid argument
1 0x004033eb: dirty_ring_collect_dirty_pages at
dirty_log_te
When execute the dirty_log_test on some aarch64 machine, it sometimes
trigger the ASSERT:
Test Assertion Failure
dirty_log_test.c:384: dirty_ring_vcpu_ring_full
pid=14854 tid=14854 errno=22 - Invalid argument
1 0x004033eb: dirty_ring_collect_dirty_pages at
dirty_log_te
