From: Nadav Amit <nadav.amit@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Nadav Amit <nadav.amit@gmail.com>
Subject: [kvm-unit-tests PATCH 0/3] x86: Running tests on bare-metal
Date: Fri, 28 Jun 2019 13:30:16 -0700 [thread overview]
Message-ID: <20190628203019.3220-1-nadav.amit@gmail.com> (raw)
This is the final bit of enabling KVM-unit-tests to run on bare-metal
environment. It requires some pending patches, which I sent before, to
be applied first.
I have run most of the tests (e.g., vmx, apic, pmu, eventinj) and they
seem to be working fine. Not all the tests run the same way they run on
KVM, of course, due to the lack of emulated devices. There are some
issues with some other tests due to failure of 1GB page allocations.
There are several known issues. On my machine I get an error due to
errtum (BDX30, BDE31, etc.):
FAIL: VMX_VMCS_ENUM.MAX_INDEX expected at least: 2e, actual: 2a
And there are also many test errors such as:
FAIL: valid link pointer: field 1418: VMREAD and VMWRITE permission:
VMX_INST_ERROR (0) is as expected (12)
These are test bugs, which Paolo and Liran know about.
It is possible to build some automation environment that builds boot
entries based on the .cfg file, but I was too busy (or lazy) to do so in
a manner that is not distribution-specific.
Nadav Amit (3):
libcflat: use stdbool
x86/vmx: Use plus for positive filters
x86: Support environments without test-devices
lib/libcflat.h | 5 +---
lib/x86/fwcfg.c | 62 +++++++++++++++++++++++++++++++++++++++++++++++
lib/x86/fwcfg.h | 4 +++
x86/apic.c | 4 ++-
x86/cstart64.S | 13 +++++++---
x86/eventinj.c | 20 ++++++++++++---
x86/unittests.cfg | 32 ++++++++++++------------
x86/vmx.c | 4 +--
x86/vmx_tests.c | 7 ++++++
9 files changed, 121 insertions(+), 30 deletions(-)
--
2.17.1
next reply other threads:[~2019-06-29 3:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 20:30 Nadav Amit [this message]
2019-06-28 20:30 ` [kvm-unit-tests PATCH 1/3] libcflat: use stdbool Nadav Amit
2019-07-02 16:08 ` Paolo Bonzini
2019-06-28 20:30 ` [kvm-unit-tests PATCH 2/3] x86/vmx: Use plus for positive filters Nadav Amit
2019-06-28 20:30 ` [kvm-unit-tests PATCH 3/3] x86: Support environments without test-devices Nadav Amit
2019-07-02 16:08 ` Paolo Bonzini
2019-07-02 16:43 ` Nadav Amit
2019-07-02 17:24 ` Paolo Bonzini
2019-07-02 17:45 ` Nadav Amit
2019-07-02 18:28 ` Paolo Bonzini
2019-07-02 23:39 ` Nadav Amit
2019-07-02 23:56 ` Nadav Amit
2019-07-03 5:39 ` Paolo Bonzini
2019-07-03 6:09 ` Nadav Amit
2019-07-15 15:48 ` Andrew Jones
2019-07-15 18:08 ` Nadav Amit
2019-07-15 18:26 ` Paolo Bonzini
2019-07-15 18:43 ` Nadav Amit
2019-07-15 18:54 ` Paolo Bonzini
2019-07-21 16:40 ` Nadav Amit
2019-07-21 16:51 ` Paolo Bonzini
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=20190628203019.3220-1-nadav.amit@gmail.com \
--to=nadav.amit@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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