[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87bla1fc0f.fsf@vitty.brq.redhat.com>
Date: Mon, 26 Apr 2021 14:47:44 +0200
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: Rong Chen <rong.a.chen@...el.com>,
kernel test robot <oliver.sang@...el.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>,
LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org,
lkp@...el.com, xudong.hao@...el.com
Subject: Re: [LKP] Re: [KVM] 4fc096a99e:
kernel-selftests.kvm.set_memory_region_test.fail
Rong Chen <rong.a.chen@...el.com> writes:
> On 4/23/21 2:23 PM, Vitaly Kuznetsov wrote:
>> kernel test robot <oliver.sang@...el.com> writes:
>>
>>> Greeting,
>>>
>>> FYI, we noticed the following commit (built with gcc-9):
>>>
>>> commit: 4fc096a99e01dd06dc55bef76ade7f8d76653245 ("KVM: Raise the
>>> maximum number of user memslots")
>> ...
>>
>>> # selftests: kvm: set_memory_region_test
>>> # Testing KVM_RUN with zero added memory regions
>>> # Allowed number of memory slots: 32764
>>> # Adding slots 0..32763, each memory region with 2048K size
>>> #
>>> not ok 32 selftests: kvm: set_memory_region_test # TIMEOUT 120 seconds
>> This is a timeout, it can be raised in
>> 'tools/testing/selftests/kvm/settings'. I assume the test is running in
>> a VM?
>>
>
> Hi Vitaly,
>
> It's running in a physical Haswell machine.
>
Ok, let's try to speed up the test. I'll send a patch.
--
Vitaly
Powered by blists - more mailing lists