Re: [PATCH v1 0/9] KVM selftests for s390x

2019-06-04 Thread Christian Borntraeger
On 04.06.19 19:19, Paolo Bonzini wrote: > On 23/05/19 18:43, Thomas Huth wrote: >> This patch series enables the KVM selftests for s390x. As a first >> test, the sync_regs from x86 has been adapted to s390x, and after >> a fix for KVM_CAP_MAX_VCPU_ID on s390x, the kvm_create_max_vcpus >> is now

Re: [PATCH v1 0/9] KVM selftests for s390x

2019-06-04 Thread Paolo Bonzini
On 23/05/19 18:43, Thomas Huth wrote: > This patch series enables the KVM selftests for s390x. As a first > test, the sync_regs from x86 has been adapted to s390x, and after > a fix for KVM_CAP_MAX_VCPU_ID on s390x, the kvm_create_max_vcpus > is now enabled here, too. > > Please note that the ucal

Re: [PATCH v1 0/9] KVM selftests for s390x

2019-05-24 Thread Christian Borntraeger
I have now queued every patch in the kselftest branch on kvms390 at kernel.org. I will push out for next as soon as I have some ack/nacks on the "KVM: s390: fix memory slot handling for KVM_SET_USER_MEMORY_REGION" patch. On 23.05.19 18:43, Thomas Huth wrote: > This patch series enables the KVM sel

Re: [PATCH v1 0/9] KVM selftests for s390x

2019-05-24 Thread Christian Borntraeger
On 24.05.19 14:36, David Hildenbrand wrote: > On 24.05.19 14:29, Christian Borntraeger wrote: >> >> >> On 24.05.19 14:17, Christian Borntraeger wrote: >>> >>> >>> On 24.05.19 13:11, Christian Borntraeger wrote: I do get [10400.440298] kvm-s390: failed to commit memory region

Re: [PATCH v1 0/9] KVM selftests for s390x

2019-05-24 Thread David Hildenbrand
On 24.05.19 14:29, Christian Borntraeger wrote: > > > On 24.05.19 14:17, Christian Borntraeger wrote: >> >> >> On 24.05.19 13:11, Christian Borntraeger wrote: >>> I do get >>> >>> [10400.440298] kvm-s390: failed to commit memory region >>> [10400.508723] kvm-s390: failed to commit memory region >

Re: [PATCH v1 0/9] KVM selftests for s390x

2019-05-24 Thread Christian Borntraeger
On 24.05.19 14:17, Christian Borntraeger wrote: > > > On 24.05.19 13:11, Christian Borntraeger wrote: >> I do get >> >> [10400.440298] kvm-s390: failed to commit memory region >> [10400.508723] kvm-s390: failed to commit memory region >> >> when running the tests. Will have a look. > > It com

Re: [PATCH v1 0/9] KVM selftests for s390x

2019-05-24 Thread Christian Borntraeger
On 24.05.19 13:11, Christian Borntraeger wrote: > I do get > > [10400.440298] kvm-s390: failed to commit memory region > [10400.508723] kvm-s390: failed to commit memory region > > when running the tests. Will have a look. It comes from kvm_vm_free. This calls KVM_SET_USER_MEMORY_REGION with

Re: [PATCH v1 0/9] KVM selftests for s390x

2019-05-24 Thread Christian Borntraeger
I do get [10400.440298] kvm-s390: failed to commit memory region [10400.508723] kvm-s390: failed to commit memory region when running the tests. Will have a look. On 23.05.19 18:43, Thomas Huth wrote: > This patch series enables the KVM selftests for s390x. As a first > test, the sync_regs from