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 v3 0/2] x86/emulator: Add some tests for loading segment descriptor in emulator
Date: Thu, 10 Feb 2022 16:46:32 +0800 [thread overview]
Message-ID: <cover.1644481282.git.houwenlong.hwl@antgroup.com> (raw)
Add some far ret and far jmp 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 v2:
- Fix some complication errors, which are not gotten in my gcc.
- Rename lret as far ret, and rename ljmp as far jmp.
Changed from v1:
- As Sean suggested, refactor the test loop to make the code simple.
v2: https://lore.kernel.org/kvm/cover.1644311445.git.houwenlong.hwl@antgroup.com
[*] https://lore.kernel.org/kvm/cover.1644292363.git.houwenlong.hwl@antgroup.com
Hou Wenlong (3):
x86/emulator: Add some tests for far ret instruction emulation
x86/emulator: Rename test_ljmp() as test_far_jmp()
x86/emulator: Add some tests for far jmp instruction emulation
x86/emulator.c | 202 +++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 188 insertions(+), 14 deletions(-)
--
2.31.1
next reply other threads:[~2022-02-10 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 8:46 Hou Wenlong [this message]
2022-02-10 8:46 ` [kvm-unit-tests PATCH v3 1/3] x86/emulator: Add some tests for far ret instruction emulation Hou Wenlong
2022-02-10 16:39 ` Sean Christopherson
2022-02-10 8:46 ` [kvm-unit-tests PATCH v3 2/3] x86/emulator: Rename test_ljmp() as test_far_jmp() Hou Wenlong
2022-02-10 16:39 ` Sean Christopherson
2022-02-10 8:46 ` [kvm-unit-tests PATCH v3 3/3] x86/emulator: Add some tests for far jmp instruction emulation Hou Wenlong
2022-02-10 16:41 ` 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.1644481282.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.