From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
xudong.hao@intel.com, Joerg Roedel <joro@8bytes.org>,
Jim Mattson <jmattson@google.com>, kvm list <kvm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org
Subject: Re: selftests: kvm: Test results on x86_64
Date: Mon, 22 Jun 2020 12:59:53 +0200 [thread overview]
Message-ID: <87r1u7fjrq.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <CA+G9fYvVfSEBsZCaiMCpCKfJNdbFzrKGdXR0KeRYG+nhDiEpuA@mail.gmail.com>
Naresh Kamboju <naresh.kamboju@linaro.org> writes:
> FYI,
> Linaro test farm selftests kvm test cases results.
> * kvm_mmio_warning_test — SKIP
> * kvm_svm_vmcall_test — SKIP
> * kvm_clear_dirty_log_test — PASS
> * kvm_cr4_cpuid_sync_test — PASS
> * kvm_debug_regs — PASS
> * kvm_demand_paging_test — PASS
> * kvm_dirty_log_test — PASS
> * kvm_evmcs_test — PASS
> * kvm_hyperv_cpuid — PASS
> * kvm_ * kvm_create_max_vcpus — PASS
> * kvm_platform_info_test — PASS
> * kvm_set_memory_region_test — PASS
> * kvm_set_sregs_test — PASS
> * kvm_smm_test — PASS
> * kvm_state_test — PASS
> * kvm_steal_time — PASS
> * kvm_sync_regs_test — PASS
> * kvm_vmx_close_while_nested_test — PASS
> * kvm_vmx_dirty_log_test — PASS
> * kvm_vmx_preemption_timer_test — PASS
> * kvm_vmx_set_nested_state_test — PASS
> * kvm_vmx_tsc_adjust_test — PASS
> * kvm_xss_msr_test — PASS
[...]
Thanks you! It would be great to see which particular commit was tested
here and how often you run these tests in general, which git/branch you
follow. Also, you can improve your subject line by adding [PASS] or
[FAIL] so we can see if there's a problem to deal with.
--
Vitaly
prev parent reply other threads:[~2020-06-22 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 9:10 Naresh Kamboju
2020-06-22 10:59 ` Vitaly Kuznetsov [this message]
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=87r1u7fjrq.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=wanpengli@tencent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®