All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Kevin Tian <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>,
	suravee.suthikulpanit@amd.com, Eddie Dong <eddie.dong@intel.com>,
	Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] x86/nHVM: generic hook adjustments
Date: Fri, 26 Jun 2015 10:09:53 +0100	[thread overview]
Message-ID: <558D16E1.8010201@citrix.com> (raw)
In-Reply-To: <558D313C020000780008A126@mail.emea.novell.com>

On 26/06/15 10:02, Jan Beulich wrote:
> Some of the generic hooks were unused altogether - drop them.
>
> Some of the hooks were used only to handle calls from the specific
> vendor's code (SVM) - drop them too.
>
> Several more hooks were pointlessly implementaed as out-of-line
> functions, when most (all?) other HVM hooks use inline ones - make
> them inlines. None of them are implemented by only one of SVM or VMX,
> so also drop the conditionals. Funnily nhvm_vmcx_hap_enabled(), having
> return type bool_t, nevertheless returned -EOPNOTSUPP.
>
> nhvm_vmcx_guest_intercepts_trap() and its hook and implementations are
> being made return bool_t, as they should have been from the beginning
> (its sole caller only checks for a non-zero result).
>
> Finally, make static whatever can as a result be static.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Reviewed-by: Andrew Cooper <andrew.cooper3@citirx.com>

That is a healthy quantity of deletion.

  reply	other threads:[~2015-06-26  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  9:02 [PATCH] x86/nHVM: generic hook adjustments Jan Beulich
2015-06-26  9:09 ` Andrew Cooper [this message]
2015-06-26 14:58 ` Boris Ostrovsky
2015-06-26 15:42   ` Jan Beulich
2015-06-26 15:50     ` Boris Ostrovsky
2015-06-26 15:56       ` Jan Beulich
2015-06-26 16:15         ` Boris Ostrovsky

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=558D16E1.8010201@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=aravind.gopalakrishnan@amd.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=eddie.dong@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xen-devel@lists.xenproject.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.