From: Rong Chen <rong.a.chen@intel.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
kernel test robot <oliver.sang@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, xudong.hao@intel.com
Subject: Re: [LKP] Re: [KVM] 4fc096a99e: kernel-selftests.kvm.set_memory_region_test.fail
Date: Sun, 25 Apr 2021 16:08:44 +0800 [thread overview]
Message-ID: <41d6e208-1cc5-9633-fda2-232a9156a824@intel.com> (raw)
In-Reply-To: <871rb1h63v.fsf@vitty.brq.redhat.com>
On 4/23/21 2:23 PM, Vitaly Kuznetsov wrote:
> kernel test robot <oliver.sang@intel.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
WARNING: multiple messages have this Message-ID (diff)
From: Rong Chen <rong.a.chen@intel.com>
To: lkp@lists.01.org
Subject: Re: [KVM] 4fc096a99e: kernel-selftests.kvm.set_memory_region_test.fail
Date: Sun, 25 Apr 2021 16:08:44 +0800 [thread overview]
Message-ID: <41d6e208-1cc5-9633-fda2-232a9156a824@intel.com> (raw)
In-Reply-To: <871rb1h63v.fsf@vitty.brq.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On 4/23/21 2:23 PM, Vitaly Kuznetsov wrote:
> kernel test robot <oliver.sang@intel.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
next prev parent reply other threads:[~2021-04-25 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 3:25 [KVM] 4fc096a99e: kernel-selftests.kvm.set_memory_region_test.fail kernel test robot
2021-04-23 3:25 ` kernel test robot
2021-04-23 6:23 ` Vitaly Kuznetsov
2021-04-23 6:23 ` Vitaly Kuznetsov
2021-04-25 8:08 ` Rong Chen [this message]
2021-04-25 8:08 ` Rong Chen
2021-04-26 12:47 ` [LKP] " Vitaly Kuznetsov
2021-04-26 12:47 ` Vitaly Kuznetsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41d6e208-1cc5-9633-fda2-232a9156a824@intel.com \
--to=rong.a.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=xudong.hao@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.