From: "Hou Wenlong" <houwenlong.hwl@antgroup.com>
To: kvm@vger.kernel.org
Cc: "Sean Christopherson" <seanjc@google.com>,
"Hou Wenlong" <houwenlong.hwl@antgroup.com>
Subject: [kvm-unit-tests PATCH v2 0/2] x86/emulator: Add some tests for loading segment descriptor in emulator
Date: Tue, 08 Feb 2022 17:30:55 +0800 [thread overview]
Message-ID: <cover.1644311445.git.houwenlong.hwl@antgroup.com> (raw)
In-Reply-To: <cover.1642669912.git.houwenlong.hwl@antgroup.com>
Add some lret and ljmp tests for the related x86 emulator bugs[*]. Those tests
would be tested both on hardware and emulator. Enable kvm.force_emulation_prefix
to test them on emulator.
Changed from v1:
- As Sean suggested, refactor the test loop to make the code simple.
[*] https://lore.kernel.org/kvm/cover.1644292363.git.houwenlong.hwl@antgroup.com
Hou Wenlong (2):
x86/emulator: Add some tests for lret instruction emulation
x86/emulator: Add some tests for ljmp instruction emulation
x86/emulator.c | 205 +++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 192 insertions(+), 13 deletions(-)
--
2.31.1
next prev parent reply other threads:[~2022-02-08 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 9:26 [kvm-unit-tests PATCH 0/2] x86/emulator: Add some tests for loading segment descriptor in emulator Hou Wenlong
2022-01-20 9:26 ` [kvm-unit-tests PATCH 1/2] x86/emulator: Add some tests for lret instruction emulation Hou Wenlong
2022-02-07 21:00 ` Sean Christopherson
2022-01-20 9:26 ` [kvm-unit-tests PATCH 2/2] x86/emulator: Add some tests for ljmp " Hou Wenlong
2022-02-08 9:30 ` Hou Wenlong [this message]
2022-02-08 9:30 ` [kvm-unit-tests PATCH v2 1/2] x86/emulator: Add some tests for lret " Hou Wenlong
2022-02-09 22:07 ` Sean Christopherson
2022-02-10 6:34 ` Hou Wenlong
2022-02-08 9:30 ` [kvm-unit-tests PATCH v2 2/2] x86/emulator: Add some tests for ljmp " Hou Wenlong
2022-02-09 22:13 ` Sean Christopherson
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=cover.1644311445.git.houwenlong.hwl@antgroup.com \
--to=houwenlong.hwl@antgroup.com \
--cc=kvm@vger.kernel.org \
--cc=seanjc@google.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.