From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Mathias Krause <minipli@grsecurity.net>
Subject: Re: [kvm-unit-tests PATCH v4 5/9] x86/access: Add forced emulation support
Date: Tue, 4 Apr 2023 16:43:02 -0700 [thread overview]
Message-ID: <ZCy2BogzCGX1qNpg@google.com> (raw)
In-Reply-To: <ZCxxIj0Go5XA6LPU@google.com>
On Tue, Apr 04, 2023, Sean Christopherson wrote:
> On Tue, Apr 04, 2023, Sean Christopherson wrote:
> > diff --git a/x86/unittests.cfg b/x86/unittests.cfg
> > index f324e32d..6194e0ea 100644
> > --- a/x86/unittests.cfg
> > +++ b/x86/unittests.cfg
> > @@ -143,6 +143,12 @@ file = access_test.flat
> > arch = x86_64
> > extra_params = -cpu max
> >
> > +[access_fep]
> > +file = access_test.flat
> > +arch = x86_64
> > +extra_params = -cpu max -append force_emulation
> > +groups = nodefault
>
> Argh, this needs to override the timeout. Ditto for the vmx_pf_exception_test_fep
> variant. If there are no other issues or objections in the series, I'll set the
> timeouts to 240 when applying.
FYI Mathias, Paolo grabbed these already but missed my mea culpas. Posted fixes
for the configs: https://lore.kernel.org/all/20230404234112.367850-1-seanjc@google.com
next prev parent reply other threads:[~2023-04-04 23:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 16:53 [kvm-unit-tests PATCH v4 0/9] x86/access: CR0.WP=0/1 r/o tests Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 1/9] x86: Use existing CR0.WP / CR4.SMEP bit definitions Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 2/9] x86/access: CR0.WP toggling write to r/o data test Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 3/9] x86/access: Replace spaces with tabs in access_test.c Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 4/9] x86/access: Use standard pass/fail reporting machinery Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 5/9] x86/access: Add forced emulation support Sean Christopherson
2023-04-04 18:49 ` Sean Christopherson
2023-04-04 23:43 ` Sean Christopherson [this message]
2023-04-05 11:29 ` Mathias Krause
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 6/9] x86/access: Try forced emulation for CR0.WP test as well Sean Christopherson
2023-04-05 11:48 ` Mathias Krause
2023-04-05 14:29 ` Sean Christopherson
2023-04-05 15:41 ` Mathias Krause
2023-04-05 19:41 ` Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 7/9] x86: Drop VPID invl tests from nested reduced MAXPHYADDR access testcase Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 8/9] x86: Mark the VPID invalidation nested VMX access tests nodefault Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 9/9] nVMX: Add forced emulation variant of #PF access test Sean Christopherson
2023-04-04 19:45 ` 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=ZCy2BogzCGX1qNpg@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=minipli@grsecurity.net \
--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 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.