From: Paolo Bonzini <pbonzini@redhat.com>
To: Ahmed Soliman <ahmedsoliman@mena.vt.edu>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, Peter Xu <peterx@redhat.com>,
linux-kernel@vger.kernel.org, Andrew Jones <drjones@redhat.com>
Subject: Re: KVM selftests are failing
Date: Fri, 16 Nov 2018 13:08:12 +0100 [thread overview]
Message-ID: <b8246d8c-a50d-2b7b-bea8-b01e945c8f30@redhat.com> (raw)
In-Reply-To: <CANBxJ=FDOpySC7w1fVbWCOy+ASO=A7WcsFiDJEcGtzWbYM6NqQ@mail.gmail.com>
On 16/11/18 13:00, Ahmed Soliman wrote:
> Hello once again,
>
> I noticed that there is still more problems with kvmself test (at
> least on my machine)
>
> Any test that would successfully reach the guest's code immediately
> VMexit by a shutdown.
>
> $ ./vmx_tsc_adjust_test
> ==== Test Assertion Failure ====
> x86_64/vmx_tsc_adjust_test.c:156: run->exit_reason == KVM_EXIT_IO
> pid=8499 tid=8499 - Success
> 1 0x00005604f07bd36c: ?? ??:0
> 2 0x00007f5c0dc53ae6: ?? ??:0
> 3 0x00005604f07bd4b9: ?? ??:0
> Got exit_reason other than KVM_EXIT_IO: 8 (SHUTDOWN)
>
> Also I have got a question I noticed 2 kvm test suites, kvm selftests
> in tools/testing/selftests/kvm/
> and this kvm unit test at [1] I am curious if I should put my tests in
> the kvm unit test intead of kvm selftest
If you are testing the API, or some corner cases and race conditions
that are hard to synthesize with a "real-world" guest, put it here. If
you are testing the emulated hardware, you probably want to put it in
kvm-unit-tests instead.
Paolo
next prev parent reply other threads:[~2018-11-16 12:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 15:30 KVM selftests are failing Ahmed Soliman
2018-11-14 18:08 ` Andrew Jones
2018-11-14 18:19 ` Anders Roxell
2018-11-14 19:23 ` Ahmed Soliman
2018-11-14 21:29 ` Ahmed Soliman
2018-11-15 9:02 ` Andrew Jones
2018-11-15 13:36 ` Ahmed Soliman
2018-11-15 14:50 ` Andrew Jones
2018-11-15 16:15 ` Ahmed Soliman
2018-11-15 16:39 ` Vitaly Kuznetsov
2018-11-16 12:00 ` Ahmed Soliman
2018-11-16 12:08 ` Paolo Bonzini [this message]
2018-11-16 13:36 ` Vitaly Kuznetsov
2018-11-17 19:43 ` Ahmed Soliman
2018-11-15 8:41 ` Andrew Jones
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=b8246d8c-a50d-2b7b-bea8-b01e945c8f30@redhat.com \
--to=pbonzini@redhat.com \
--cc=ahmedsoliman@mena.vt.edu \
--cc=anders.roxell@linaro.org \
--cc=drjones@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=shuah@kernel.org \
--cc=vkuznets@redhat.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