From: Sean Christopherson <seanjc@google.com>
To: Aaron Lewis <aaronlewis@google.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, jmattson@google.com
Subject: Re: [kvm-unit-tests PATCH v2 3/4] x86: Add a test framework for nested_vmx_reflect_vmexit() testing
Date: Thu, 20 Jan 2022 00:46:04 +0000 [thread overview]
Message-ID: <YeiwzMT/7AQcJsvd@google.com> (raw)
In-Reply-To: <CAAAPnDG+eoE42se67ZFaeBG7H6QeAwx2LpZuVqKuXL_eY4eq=g@mail.gmail.com>
On Wed, Jan 19, 2022, Aaron Lewis wrote:
> >
> > > diff --git a/x86/unittests.cfg b/x86/unittests.cfg
> > > index 9fcdcae..0353b69 100644
> > > --- a/x86/unittests.cfg
> > > +++ b/x86/unittests.cfg
> > > @@ -368,6 +368,13 @@ arch = x86_64
> > > groups = vmx nested_exception
> > > check = /sys/module/kvm_intel/parameters/allow_smaller_maxphyaddr=Y
> > >
> > > +[vmx_exception_test]
> > > +file = vmx.flat
> > > +extra_params = -cpu max,+vmx -append vmx_exception_test
> > > +arch = x86_64
> > > +groups = vmx nested_exception
> > > +timeout = 10
> >
> > Why add a new test case instead of folding this into "vmx"? It's quite speedy.
> > The "vmx" bucket definitely needs some cleanup, but I don't thinking adding a bunch
> > of one-off tests is the way forward.
> >
>
> I'm not sure I follow. The test does run in the "vmx" bucket
> AFAICT... Oh, do you mean it should be added to the extra_params here
> along with the other tests?
Yep, exactly. "vmx" really needs to be split up and/or reworked so that it's
command line isn't so ridiculous, but that's a future problem.
next prev parent reply other threads:[~2022-01-20 0:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 1:18 [kvm-unit-tests PATCH v2 0/4] Add additional testing for routing L2 exceptions Aaron Lewis
2021-12-14 1:18 ` [kvm-unit-tests PATCH v2 1/4] x86: Fix a #GP from occurring in usermode library's exception handlers Aaron Lewis
2021-12-14 1:18 ` [kvm-unit-tests PATCH v2 2/4] x86: Align L2's stacks Aaron Lewis
2022-01-12 19:38 ` Sean Christopherson
2021-12-14 1:18 ` [kvm-unit-tests PATCH v2 3/4] x86: Add a test framework for nested_vmx_reflect_vmexit() testing Aaron Lewis
2022-01-12 20:48 ` Sean Christopherson
2022-01-19 16:57 ` Aaron Lewis
2022-01-20 0:46 ` Sean Christopherson [this message]
2021-12-14 1:18 ` [kvm-unit-tests PATCH v2 4/4] x86: Add test coverage " Aaron Lewis
2021-12-14 12:19 ` [kvm-unit-tests PATCH v2 0/4] Add additional testing for routing L2 exceptions Paolo Bonzini
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=YeiwzMT/7AQcJsvd@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=jmattson@google.com \
--cc=kvm@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 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.