From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Sergey Dyasli <sergey.dyasli@citrix.com>, xen-devel@lists.xen.org
Cc: Kevin Tian <kevin.tian@intel.com>,
Jan Beulich <jbeulich@suse.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH v2 0/4] x86/vvmx: correctly emulate VMREAD and VMWRITE
Date: Mon, 6 Feb 2017 15:19:15 +0000 [thread overview]
Message-ID: <cc17c037-c74d-cacd-335c-6549ee92d1b9@citrix.com> (raw)
In-Reply-To: <20170206145747.13885-1-sergey.dyasli@citrix.com>
On 06/02/17 14:57, Sergey Dyasli wrote:
> Currently, emulation of vmread and vmwrite for a guest leads to BUG()
> in cases when actual VMREAD or VMWRITE ends up in VMfail due to invalid
> arguments. The goal of this patch series is to prevent the BUG() from
> happening and report any kind of VMfail back to the guest, just like
> it would be done by H/W.
>
> v1 --> v2:
> * Removed "ASM_FLAG_OUT" from tools/tests/x86_emulator/x86_emulate.h
> * Replaced "~0UL" with "~0" for VMX_INSN_FAIL_INVALID
> * Removed double underscore prefix from vmwrite_safe() and vmread_safe()
> * Replaced "setb --> setc" and "sete --> setz"
> * Removed "fail_" prefix from "invalid" and "valid" asm constraints
> * Added "\t" to asm
> * Added unlikely() for checking fail conditions
> * Moved "ASM_FLAG_OUT" from lib.h to asm_defns.h
>
> Sergey Dyasli (4):
> x86/vmx: introduce vmwrite_safe()
> x86/vmx: improve vmread_safe()
> x86/vvmx: correctly emulate VMWRITE
> x86/vvmx: correctly emulate VMREAD
All 4 Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> xen/arch/x86/hvm/vmx/vmcs.c | 20 +++++++----
> xen/arch/x86/hvm/vmx/vvmx.c | 46 +++++++++++++++++++-----
> xen/include/asm-x86/asm_defns.h | 6 ++++
> xen/include/asm-x86/hvm/vmx/vmcs.h | 6 ++--
> xen/include/asm-x86/hvm/vmx/vmx.h | 72 +++++++++++++++++++++++++-------------
> xen/include/asm-x86/hvm/vmx/vvmx.h | 11 ++++--
> 6 files changed, 117 insertions(+), 44 deletions(-)
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-02-06 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 14:57 [PATCH v2 0/4] x86/vvmx: correctly emulate VMREAD and VMWRITE Sergey Dyasli
2017-02-06 14:57 ` [PATCH v2 1/4] x86/vmx: introduce vmwrite_safe() Sergey Dyasli
2017-02-07 6:31 ` Tian, Kevin
2017-02-07 11:09 ` Jan Beulich
2017-02-07 11:59 ` Andrew Cooper
2017-02-07 13:18 ` Jan Beulich
2017-02-07 15:06 ` Sergey Dyasli
2017-02-07 15:22 ` Andrew Cooper
2017-02-07 16:22 ` Jan Beulich
2017-02-07 16:34 ` Andrew Cooper
2017-02-07 16:47 ` Jan Beulich
2017-02-06 14:57 ` [PATCH v2 2/4] x86/vmx: improve vmread_safe() Sergey Dyasli
2017-02-07 6:32 ` Tian, Kevin
2017-02-06 14:57 ` [PATCH v2 3/4] x86/vvmx: correctly emulate VMWRITE Sergey Dyasli
2017-02-07 6:37 ` Tian, Kevin
2017-02-06 14:57 ` [PATCH v2 4/4] x86/vvmx: correctly emulate VMREAD Sergey Dyasli
2017-02-07 6:52 ` Tian, Kevin
2017-02-07 15:56 ` Sergey Dyasli
2017-02-06 15:19 ` Andrew Cooper [this message]
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=cc17c037-c74d-cacd-335c-6549ee92d1b9@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=sergey.dyasli@citrix.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).