From: Paolo Bonzini <pbonzini@redhat.com>
To: Bandan Das <bsd@redhat.com>, kvm@vger.kernel.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH kvm-unit-tests v2 0/3] More nvmx unit tests changes
Date: Tue, 10 Jun 2014 08:51:56 +0200 [thread overview]
Message-ID: <5396AB0C.1070404@redhat.com> (raw)
In-Reply-To: <1402347894-13659-1-git-send-email-bsd@redhat.com>
Il 09/06/2014 23:04, Bandan Das ha scritto:
> A couple more updates to test_vmxon, test_vmptrld
> and test_vmclear based on kvm commits -
>
> 3573e22cfecaac83f82ef4f6847d90e466fc8e10
> KVM: nVMX: additional checks on vmxon region
>
> 96ec146330d18a938b4773be8d6dd1f93399507c
> KVM: nVMX: fail on invalid vmclear/vmptrld pointer
>
> v2:
> - 1/3(New): Move the writing of flags register inside asm blocks
>
> Bandan Das (3):
> VMX: move write_rflags inside asm blocks for vmx instructions
> VMX: Add more checks to test_vmxon
> VMX: Updated test_vmclear and test_vmptrld
>
> lib/x86/processor.h | 7 ---
> x86/vmx.c | 121 +++++++++++++++++++++++++++++++++++++++++-----------
> x86/vmx.h | 10 ++++-
> 3 files changed, 103 insertions(+), 35 deletions(-)
>
Sooner or later, we probably want to return the flags so that you can
test for CF=1 or ZF=1. For now, I've applied the patch. Thanks!
Paolo
next prev parent reply other threads:[~2014-06-10 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 21:04 [PATCH kvm-unit-tests v2 0/3] More nvmx unit tests changes Bandan Das
2014-06-09 21:04 ` [PATCH kvm-unit-tests v2 1/3] VMX: move write_rflags inside asm blocks for vmx instructions Bandan Das
2014-06-09 21:04 ` [PATCH kvm-unit-tests v2 2/3] VMX: Add more checks to test_vmxon Bandan Das
2014-06-09 21:04 ` [PATCH kvm-unit-tests v2 3/3] VMX: Updated test_vmclear and test_vmptrld Bandan Das
2014-06-10 6:51 ` Paolo Bonzini [this message]
2014-06-19 11:41 ` [PATCH kvm-unit-tests v2 0/3] More nvmx unit tests changes 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=5396AB0C.1070404@redhat.com \
--to=pbonzini@redhat.com \
--cc=bsd@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
/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.