From: Sean Christopherson <seanjc@google.com>
To: David Matlack <dmatlack@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Jim Mattson <jmattson@google.com>, Peter Xu <peterx@redhat.com>,
Colton Lewis <coltonlewis@google.com>,
Aaron Lewis <aaronlewis@google.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH v2 8/8] KVM: selftest: Add a test for KVM_CAP_EXIT_ON_EMULATION_FAILURE
Date: Fri, 28 Oct 2022 00:34:17 +0000 [thread overview]
Message-ID: <Y1sjicBP104CUAtM@google.com> (raw)
In-Reply-To: <20221018214612.3445074-9-dmatlack@google.com>
s/selftest/selftests
On Tue, Oct 18, 2022, David Matlack wrote:
> diff --git a/tools/testing/selftests/kvm/.gitignore b/tools/testing/selftests/kvm/.gitignore
> index c484ff164000..22807badd510 100644
> --- a/tools/testing/selftests/kvm/.gitignore
> +++ b/tools/testing/selftests/kvm/.gitignore
> @@ -16,6 +16,7 @@
> /x86_64/cr4_cpuid_sync_test
> /x86_64/debug_regs
> /x86_64/evmcs_test
> +/x86_64/exit_on_emulation_failure_test
> /x86_64/fix_hypercall_test
> /x86_64/get_msr_index_features
> /x86_64/kvm_clock_test
> diff --git a/tools/testing/selftests/kvm/Makefile b/tools/testing/selftests/kvm/Makefile
> index 90c19e1753f7..55b6f4efa57c 100644
> --- a/tools/testing/selftests/kvm/Makefile
> +++ b/tools/testing/selftests/kvm/Makefile
> @@ -81,6 +81,7 @@ TEST_GEN_PROGS_x86_64 = x86_64/cpuid_test
> TEST_GEN_PROGS_x86_64 += x86_64/cr4_cpuid_sync_test
> TEST_GEN_PROGS_x86_64 += x86_64/get_msr_index_features
> TEST_GEN_PROGS_x86_64 += x86_64/evmcs_test
> +TEST_GEN_PROGS_x86_64 += x86_64/exit_on_emulation_failure_test
We really should figure out an automation solution, both for .gitignore (easier)
and for selecting which binaries to compile. The makefile especially is getting
unwieldy.
prev parent reply other threads:[~2022-10-28 0:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 21:46 [PATCH v2 0/8] KVM: selftests: Fix and clean up emulator_error_test David Matlack
2022-10-18 21:46 ` [PATCH v2 1/8] KVM: selftests: Rename emulator_error_test to smaller_maxphyaddr_emulation_test David Matlack
2022-10-27 23:27 ` Sean Christopherson
2022-10-18 21:46 ` [PATCH v2 2/8] KVM: selftests: Explicitly require instructions bytes David Matlack
2022-10-27 23:41 ` Sean Christopherson
2022-10-18 21:46 ` [PATCH v2 3/8] KVM: selftests: Delete dead ucall code David Matlack
2022-10-27 23:44 ` Sean Christopherson
2022-10-28 23:59 ` David Matlack
2022-10-18 21:46 ` [PATCH v2 4/8] KVM: selftests: Move flds instruction emulation failure handling to header David Matlack
2022-10-18 21:46 ` [PATCH v2 5/8] KVM: x86/mmu: Use BIT{,_ULL}() for PFERR masks David Matlack
2022-10-27 23:45 ` Sean Christopherson
2022-10-18 21:46 ` [PATCH v2 6/8] KVM: selftests: Copy KVM PFERR masks into selftests David Matlack
2022-10-28 0:34 ` Sean Christopherson
2022-10-18 21:46 ` [PATCH v2 7/8] KVM: selftests: Expect #PF(RSVD) when TDP is disabled David Matlack
2022-10-28 0:31 ` Sean Christopherson
2022-10-28 23:51 ` David Matlack
2022-10-31 16:47 ` Sean Christopherson
2022-10-18 21:46 ` [PATCH v2 8/8] KVM: selftest: Add a test for KVM_CAP_EXIT_ON_EMULATION_FAILURE David Matlack
2022-10-28 0:34 ` 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=Y1sjicBP104CUAtM@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=coltonlewis@google.com \
--cc=dmatlack@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@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 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.