[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2f1f36b-51b6-30f3-cee5-950b72b6fa67@redhat.com>
Date: Fri, 24 May 2019 14:36:24 +0200
From: David Hildenbrand <david@...hat.com>
To: Christian Borntraeger <borntraeger@...ibm.com>,
Thomas Huth <thuth@...hat.com>,
Janosch Frank <frankja@...ux.ibm.com>, kvm@...r.kernel.org
Cc: Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Shuah Khan <shuah@...nel.org>,
Cornelia Huck <cohuck@...hat.com>,
Andrew Jones <drjones@...hat.com>,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-s390@...r.kernel.org
Subject: Re: [PATCH v1 0/9] KVM selftests for s390x
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
>>>
>>> when running the tests. Will have a look.
>>
>> It comes from kvm_vm_free. This calls KVM_SET_USER_MEMORY_REGION with size 0,
>> which the s390 code does not like.
>>
>
> The doc says about KVM_SET_USER_MEMORY_REGION:
>
> This ioctl allows the user to create or modify a guest physical memory
> slot. When changing an existing slot, it may be moved in the guest
> physical memory space, or its flags may be modified. --> It may not be
> resized. <----
Size 0 is deleting, not resizing AFAIK.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists