From: Jan Kiszka <jan.kiszka@web.de>
To: Arthur Chunqi Li <yzt356@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Gleb Natapov <gleb@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [RFC PATCH] kvm-unit-tests : Basic architecture of VMX nested test case
Date: Wed, 24 Jul 2013 12:03:52 +0200 [thread overview]
Message-ID: <51EFA688.9040504@web.de> (raw)
In-Reply-To: <CABpY8ML=GvsbSZqkAo2Vnt1EtUZO60QVZ2F3H9T+N35SeP7Pcw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2168 bytes --]
On 2013-07-24 11:56, Arthur Chunqi Li wrote:
> So what about this one. I merged all the exit reason to "ret" and
> remove the flag detection after vmlaunch/vmresume (because I think
> this detection is useless). Currently we support only one guest, so
> variant "launched" is located in vmx_run(). If we want to support
> multiple guest, we could move it to some structures (e.g.
> environment_ctxt). Now I just put it here.
>
> static int vmx_run()
> {
> u32 ret = 0;
> bool launched = 0;
>
> asm volatile(
> "mov %%rsp, %%rsi\n\t"
> "mov %2, %%edi\n\t"
> "call vmcs_write\n\t"
>
> "0: "
> LOAD_GPR_C
> "cmp $0, %1\n\t"
> "jne 1f\n\t"
> "vmlaunch\n\t"
> SAVE_GPR_C
> /* vmlaunch error, return VMX_TEST_LAUNCH_ERR */
> "mov %3, %0\n\t"
> "jmp 2f\n\t"
> "1: "
> "vmresume\n\t"
> SAVE_GPR_C
> /* vmresume error, return VMX_TEST_RESUME_ERR */
> "mov %4, %0\n\t"
> "jmp 2f\n\t"
Where do you store the flags now? You may want to differentiate / test
if ZF of CF is set.
Jan
> "vmx_return:\n\t"
> SAVE_GPR_C
> "call exit_handler\n\t"
> /* set launched = 1 */
> "mov $0x1, %1\n\t"
> "cmp %5, %%eax\n\t"
> "je 0b\n\t"
> "mov %%eax, %0\n\t"
> "2: "
> : "=r"(ret), "=r"(launched)
> : "i"(HOST_RSP), "i"(VMX_TEST_LAUNCH_ERR),
> "i"(VMX_TEST_RESUME_ERR), "i"(VMX_TEST_RESUME)
> : "rax", "rbx", "rdi", "rsi",
> "r8", "r9", "r10", "r11", "r12", "r13", "r14", "r15",
> "memory", "cc"
> );
> switch (ret) {
> case VMX_TEST_VMEXIT:
> return 0;
> case VMX_TEST_LAUNCH_ERR:
> printf("%s : vmlaunch failed.\n", __func__);
> break;
> case VMX_TEST_RESUME_ERR:
> printf("%s : vmresume failed.\n", __func__);
> break;
> default:
> printf("%s : unhandled ret from exit_handler, ret=%d.\n",
> __func__, ret);
> break;
> }
> return 1;
> }
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-07-24 10:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 18:54 [RFC PATCH] kvm-unit-tests : Basic architecture of VMX nested test case Arthur Chunqi Li
2013-07-18 5:52 ` Paolo Bonzini
2013-07-18 7:26 ` Gleb Natapov
2013-07-18 10:47 ` Paolo Bonzini
2013-07-18 11:06 ` Gleb Natapov
2013-07-18 12:08 ` Paolo Bonzini
2013-07-18 14:11 ` Arthur Chunqi Li
2013-07-18 19:57 ` Gleb Natapov
2013-07-19 6:42 ` Paolo Bonzini
2013-07-19 9:40 ` Gleb Natapov
2013-07-19 12:06 ` Paolo Bonzini
2013-07-24 6:11 ` Arthur Chunqi Li
2013-07-24 6:40 ` Paolo Bonzini
2013-07-24 6:46 ` Arthur Chunqi Li
2013-07-24 6:48 ` Paolo Bonzini
2013-07-24 8:48 ` Arthur Chunqi Li
2013-07-24 8:53 ` Jan Kiszka
2013-07-24 9:16 ` Paolo Bonzini
2013-07-24 9:56 ` Arthur Chunqi Li
2013-07-24 10:03 ` Jan Kiszka [this message]
2013-07-24 10:16 ` Arthur Chunqi Li
2013-07-24 10:24 ` Jan Kiszka
2013-07-24 11:20 ` Arthur Chunqi Li
2013-07-24 11:25 ` Jan Kiszka
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=51EFA688.9040504@web.de \
--to=jan.kiszka@web.de \
--cc=gleb@redhat.com \
--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 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.