[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41d6e208-1cc5-9633-fda2-232a9156a824@intel.com>
Date: Sun, 25 Apr 2021 16:08:44 +0800
From: Rong Chen <rong.a.chen@...el.com>
To: Vitaly Kuznetsov <vkuznets@...hat.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
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.
Best Regards,
Rong Chen
Powered by blists - more mailing lists