From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Haozhong Zhang <haozhong.zhang@intel.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: [RFC PATCH] vvmx: replace vmreturn() by vmsucceed() and vmfail*()
Date: Wed, 14 Dec 2016 11:55:12 +0000 [thread overview]
Message-ID: <b95f0afc-ccf6-3d5e-4995-1974880f21ef@citrix.com> (raw)
In-Reply-To: <20161214112921.22830-1-haozhong.zhang@intel.com>
On 14/12/16 11:29, Haozhong Zhang wrote:
> Replace vmreturn() by vmsucceed(), vmfail(), vmfail_valid() and
> vmfail_invalid(), which are consistent to the pseudo code on Intel
> SDM, and allow to return VM instruction error numbers to L1
> hypervisor.
>
> Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> ---
> * This patch is based on my patchset "[PATCH v2 0/4] vvmx: fix L1 vmxon".
>
> * I'm not sure whether this patch by itself makes sense or should be sent
> with additional bugfix patches, so I tag it as RFC. Explanation: besides
> returning error numbers, this patch does not fix other bugs in the individual
> nvmx_handle_*() function, so the error numbers used (especially) for L1
> vmclear, vmptrld and vmwrite are still inconsistent to Intel SDM, or even
> incorrect.
If I were doing this work, I would purposefully split an API improvement
like this into a separate patch(s) as bugfixes to do with the use of the
API.
I think a change like this is fine even without the other bugfixes, as
it is still an improvement. (Of course, if you have time, it would
certainly be better to do the other bugfixes as well).
As for the patch itself, LGTM.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-14 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 11:29 [RFC PATCH] vvmx: replace vmreturn() by vmsucceed() and vmfail*() Haozhong Zhang
2016-12-14 11:55 ` Andrew Cooper [this message]
2016-12-14 13:51 ` Haozhong Zhang
2016-12-14 15:51 ` Konrad Rzeszutek Wilk
2016-12-15 12:01 ` Haozhong Zhang
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=b95f0afc-ccf6-3d5e-4995-1974880f21ef@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=haozhong.zhang@intel.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.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).