mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <ynorov@caviumnetworks.com>
To: Jan Dakinevich <jan.dakinevich@gmail.com>
Cc: <kvm@vger.kernel.org>, <pbonzini@redhat.com>,
	<rkrcmar@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: nVMX: expose INS/OUTS information support
Date: Mon, 5 Sep 2016 12:19:13 +0300	[thread overview]
Message-ID: <20160905091913.GA22817@yury-N73SV> (raw)
In-Reply-To: <1473013395-12214-1-git-send-email-jan.dakinevich@gmail.com>

On Sun, Sep 04, 2016 at 09:23:15PM +0300, Jan Dakinevich wrote:
> Expose the feature to L1 hypervisor if host CPU supports it, since
> certain hypervisors requires it for own purposes.
> 
> According to Intel SDM A.1, if CPU supports the feature,
> VMX_INSTRUCTION_INFO field of VMCS will contain detailed information
> about INS/OUTS instructions handling. This field is already copied to
> VMCS12 for L1 hypervisor (see prepare_vmcs12 routine) independently
> feature presence.
> 
> Signed-off-by: Jan Dakinevich <jan.dakinevich@gmail.com>
> ---
>  arch/x86/kvm/vmx.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index a4bb2bd..4fd22a6 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -939,6 +939,7 @@ static DEFINE_SPINLOCK(vmx_vpid_lock);
>  static struct vmcs_config {
>  	int size;
>  	int order;
> +	u32 basic_cap;
>  	u32 revision_id;
>  	u32 pin_based_exec_ctrl;
>  	u32 cpu_based_exec_ctrl;
> @@ -1215,6 +1216,11 @@ static inline bool cpu_has_vmx_ple(void)
>  		SECONDARY_EXEC_PAUSE_LOOP_EXITING;
>  }
>  
> +static inline bool cpu_has_vmx_basic_inout(void)

inline is useless. See Documentation/CodingStyle, Chapter 15

> +{
> +	return	(((u64)vmcs_config.basic_cap << 32) & VMX_BASIC_INOUT);

You can shift VMX_BASIC_INOUT (at compile time) and avoid the shifting of 
vmcs_config.basic_cap at runtime.

> +}
> +
>  static inline bool cpu_need_virtualize_apic_accesses(struct kvm_vcpu *vcpu)
>  {
>  	return flexpriority_enabled && lapic_in_kernel(vcpu);
> @@ -2877,6 +2883,8 @@ static int vmx_get_vmx_msr(struct kvm_vcpu *vcpu, u32 msr_index, u64 *pdata)
>  		*pdata = VMCS12_REVISION | VMX_BASIC_TRUE_CTLS |
>  			   ((u64)VMCS12_SIZE << VMX_BASIC_VMCS_SIZE_SHIFT) |
>  			   (VMX_BASIC_MEM_TYPE_WB << VMX_BASIC_MEM_TYPE_SHIFT);
> +		if (cpu_has_vmx_basic_inout())
> +			*pdata |= VMX_BASIC_INOUT;
>  		break;
>  	case MSR_IA32_VMX_TRUE_PINBASED_CTLS:
>  	case MSR_IA32_VMX_PINBASED_CTLS:
> @@ -3458,6 +3466,7 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf)
>  
>  	vmcs_conf->size = vmx_msr_high & 0x1fff;
>  	vmcs_conf->order = get_order(vmcs_config.size);
> +	vmcs_conf->basic_cap = vmx_msr_high;
>  	vmcs_conf->revision_id = vmx_msr_low;
>  
>  	vmcs_conf->pin_based_exec_ctrl = _pin_based_exec_control;
> -- 
> 1.9.1

  reply	other threads:[~2016-09-05  9:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04 18:23 Jan Dakinevich
2016-09-05  9:19 ` Yury Norov [this message]
2016-09-05 13:27   ` Paolo Bonzini
2016-09-05 13:27 ` Paolo Bonzini
2016-09-05 14:47   ` [PATCH v2] " Jan Dakinevich
2016-09-05 14:50     ` 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=20160905091913.GA22817@yury-N73SV \
    --to=ynorov@caviumnetworks.com \
    --cc=jan.dakinevich@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®