From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] KVM: selftests: Fastops DIV testcases
Date: Mon, 15 Sep 2025 17:25:53 -0700 [thread overview]
Message-ID: <175798203762.623957.146740047246949369.b4-ty@google.com> (raw)
In-Reply-To: <20250909202835.333554-1-seanjc@google.com>
On Tue, 09 Sep 2025 13:28:31 -0700, Sean Christopherson wrote:
> Add DIV and IDIV support to the so called fastops test to add coverage for #DE
> (the only exception that can occur during fastops execution), which was broken
> due to a typo in PeterZ's overhaul[*].
>
> I meant to post this back in July and forgot...
>
> [*] https://lore.kernel.org/all/aIF7ZhWZxlkcpm4y@google.com
>
> [...]
Applied to kvm-x86 selftests, thanks!
[1/4] KVM: selftests: Add support for #DE exception fixup
https://github.com/kvm-x86/linux/commit/7b39b6c76942
[2/4] KVM: selftests: Add coverage for 'b' (byte) sized fastops emulation
https://github.com/kvm-x86/linux/commit/9bf5da1ca427
[3/4] KVM: selftests: Dedup the gnarly constraints of the fastops tests (more macros!)
https://github.com/kvm-x86/linux/commit/fe08478b1d51
[4/4] KVM: selftests: Add support for DIV and IDIV in the fastops test
https://github.com/kvm-x86/linux/commit/aebc62b3dedc
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2025-09-16 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 20:28 Sean Christopherson
2025-09-09 20:28 ` [PATCH 1/4] KVM: selftests: Add support for #DE exception fixup Sean Christopherson
2025-09-09 20:28 ` [PATCH 2/4] KVM: selftests: Add coverage for 'b' (byte) sized fastops emulation Sean Christopherson
2025-09-09 20:28 ` [PATCH 3/4] KVM: selftests: Dedup the gnarly constraints of the fastops tests (more macros!) Sean Christopherson
2025-09-09 20:28 ` [PATCH 4/4] KVM: selftests: Add support for DIV and IDIV in the fastops test Sean Christopherson
2025-09-16 0:25 ` Sean Christopherson [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=175798203762.623957.146740047246949369.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®