From: Gleb Natapov <gleb@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Arthur Chunqi Li <yzt356@gmail.com>,
kvm@vger.kernel.org, jan.kiszka@web.de
Subject: Re: [PATCH] kvm-unit-tests : The first version of VMX nested test case
Date: Tue, 16 Jul 2013 18:20:35 +0300 [thread overview]
Message-ID: <20130716152035.GB8981@redhat.com> (raw)
In-Reply-To: <51E52035.1050401@redhat.com>
On Tue, Jul 16, 2013 at 12:28:05PM +0200, Paolo Bonzini wrote:
> > +void vmx_exit(void)
> > +{
> > + test_vmxoff();
> > + printf("\nSUMMARY: %d tests, %d failures\n", tests, fails);
> > + exit(fails ? -1 : 0);
> > +}
>
> Can you try to jump back to main, and do test_vmxoff there? This will
> avoid having to write our tests in callback style, which is a pain.
> Basically something similar to setjmp/longjmp. In main:
>
> if (setjmp(jmpbuf) == 0) {
> vmx_run();
> /* Should not reach here */
> report("test vmlaunch", 0);
> }
> test_vmxoff();
>
> exit:
> printf("\nSUMMARY: %d tests, %d failures\n", tests, fails);
> return fails ? 1 : 0;
>
> In vmx_handler:
>
> case VMX_HLT:
> printf("\nVM exit.\n");
> longjmp(jmpbuf, 1);
>
Why not just make vmexit occur after vmlaunch/vmresume like KVM does. It
will make code much more straightforward and easer to follow.
--
Gleb.
next prev parent reply other threads:[~2013-07-16 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 9:27 [PATCH] kvm-unit-tests : The first version of VMX nested test case Arthur Chunqi Li
2013-07-16 9:35 ` Arthur Chunqi Li
2013-07-16 9:45 ` Gleb Natapov
2013-07-16 9:53 ` Arthur Chunqi Li
2013-07-16 9:58 ` Gleb Natapov
2013-07-16 10:28 ` Paolo Bonzini
2013-07-16 11:47 ` Arthur Chunqi Li
2013-07-16 11:58 ` Paolo Bonzini
2013-07-16 15:20 ` Gleb Natapov [this message]
2013-07-16 15:29 ` Arthur Chunqi Li
2013-07-16 16:45 ` Gleb Natapov
2013-07-16 17:13 ` Arthur Chunqi Li
2013-07-16 17:24 ` Paolo Bonzini
2013-07-16 17:47 ` Gleb Natapov
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=20130716152035.GB8981@redhat.com \
--to=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=yzt356@gmail.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