Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Andrew Jones
On Mon, Aug 26, 2019 at 07:22:44PM +0800, Peter Xu wrote: > On Mon, Aug 26, 2019 at 01:09:58PM +0200, Andrew Jones wrote: > > On Mon, Aug 26, 2019 at 03:57:28PM +0800, Peter Xu wrote: > > > The dirty_log_test is failing on some old machines like Xeon E3-1220 > > > with tripple faults when writting

Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Peter Xu
On Mon, Aug 26, 2019 at 06:47:57PM +0800, Peter Xu wrote: > On Mon, Aug 26, 2019 at 10:25:55AM +0200, Vitaly Kuznetsov wrote: > > Peter Xu writes: > > > > > The dirty_log_test is failing on some old machines like Xeon E3-1220 > > > with tripple faults when writting to the tracked memory region:

Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Vitaly Kuznetsov
Peter Xu writes: > On Mon, Aug 26, 2019 at 10:25:55AM +0200, Vitaly Kuznetsov wrote: >> Peter Xu writes: >> >> > The dirty_log_test is failing on some old machines like Xeon E3-1220 >> > with tripple faults when writting to the tracked memory region: >> >> s,writting,writing, >> >> > >> >

Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Peter Xu
On Mon, Aug 26, 2019 at 01:09:58PM +0200, Andrew Jones wrote: > On Mon, Aug 26, 2019 at 03:57:28PM +0800, Peter Xu wrote: > > The dirty_log_test is failing on some old machines like Xeon E3-1220 > > with tripple faults when writting to the tracked memory region: > > > > Test iterations: 32,

Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Andrew Jones
On Mon, Aug 26, 2019 at 03:57:28PM +0800, Peter Xu wrote: > The dirty_log_test is failing on some old machines like Xeon E3-1220 > with tripple faults when writting to the tracked memory region: > > Test iterations: 32, interval: 10 (ms) > Testing guest mode: PA-bits:52, VA-bits:48, 4K pages

Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Peter Xu
On Mon, Aug 26, 2019 at 10:25:55AM +0200, Vitaly Kuznetsov wrote: > Peter Xu writes: > > > The dirty_log_test is failing on some old machines like Xeon E3-1220 > > with tripple faults when writting to the tracked memory region: > > s,writting,writing, > > > > > Test iterations: 32, interval:

Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Vitaly Kuznetsov
Peter Xu writes: > The dirty_log_test is failing on some old machines like Xeon E3-1220 > with tripple faults when writting to the tracked memory region: s,writting,writing, > > Test iterations: 32, interval: 10 (ms) > Testing guest mode: PA-bits:52, VA-bits:48, 4K pages > guest physical

Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Peter Xu
On Mon, Aug 26, 2019 at 10:11:34AM +0200, Thomas Huth wrote: > On 26/08/2019 09.57, Peter Xu wrote: > > The dirty_log_test is failing on some old machines like Xeon E3-1220 > > with tripple faults when writting to the tracked memory region: > > > > Test iterations: 32, interval: 10 (ms) > >

Re: [PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Thomas Huth
On 26/08/2019 09.57, Peter Xu wrote: > The dirty_log_test is failing on some old machines like Xeon E3-1220 > with tripple faults when writting to the tracked memory region: > > Test iterations: 32, interval: 10 (ms) > Testing guest mode: PA-bits:52, VA-bits:48, 4K pages > guest physical

[PATCH] KVM: selftests: Detect max PA width from cpuid

2019-08-26 Thread Peter Xu
The dirty_log_test is failing on some old machines like Xeon E3-1220 with tripple faults when writting to the tracked memory region: Test iterations: 32, interval: 10 (ms) Testing guest mode: PA-bits:52, VA-bits:48, 4K pages guest physical test memory offset: 0x7fbffef000 Test