All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH] Don't map nested_vmcb on INTERCEPT_MSR_PROT
Date: Fri, 4 Sep 2009 14:05:21 -0300	[thread overview]
Message-ID: <20090904170521.GA6591@amt.cnet> (raw)
In-Reply-To: <1251989512-22072-1-git-send-email-agraf@suse.de>

On Thu, Sep 03, 2009 at 04:51:52PM +0200, Alexander Graf wrote:
> Thanks to Joerg's previous series of cleanups, we now have almost all
> information we need to decide what to do on #VMEXIT because we get
> the variables from the VMCB on VMRUN.
> 
> Unfortunately there's one piece that slipped through the conversion,
> namely the MSR intercept which still tries to map the nested VMCB
> to find out if MSRs are intercepted.
> 
> So let's use the cached value, removing the need for two atomic maps
> (which breaks anyways) and fix an oops along the way.
> 
> CC: Joerg Roedel <joerg.roedel@amd.com>
> Signed-off-by: Alexander Graf <agraf@suse.de>

Applied, thanks.

BTW, why nested_svm_map takes mmap_sem? Thats looks wrong.

> 
> ---
> 
> v1 -> v2:
> 
>   - Don't break when MSR is not intercepted
> ---
>  arch/x86/kvm/svm.c |   15 ++++++---------
>  1 files changed, 6 insertions(+), 9 deletions(-)
> 
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index 2df9b45..a5f90c7 100644
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -1427,19 +1427,17 @@ static bool nested_svm_exit_handled_msr(struct vcpu_svm *svm)
>  {
>  	u32 param = svm->vmcb->control.exit_info_1 & 1;
>  	u32 msr = svm->vcpu.arch.regs[VCPU_REGS_RCX];
> -	struct vmcb *nested_vmcb;
>  	bool ret = false;
>  	u32 t0, t1;
>  	u8 *msrpm;
>  
> -	nested_vmcb = nested_svm_map(svm, svm->nested.vmcb, KM_USER0);
> -	msrpm       = nested_svm_map(svm, svm->nested.vmcb_msrpm, KM_USER1);
> +	if (!(svm->nested.intercept & (1ULL << INTERCEPT_MSR_PROT)))
> +		return false;
>  
> -	if (!nested_vmcb || !msrpm)
> -		goto out;
> +	msrpm = nested_svm_map(svm, svm->nested.vmcb_msrpm, KM_USER0);
>  
> -	if (!(nested_vmcb->control.intercept & (1ULL << INTERCEPT_MSR_PROT)))
> -		return 0;
> +	if (!msrpm)
> +		goto out;
>  
>  	switch (msr) {
>  	case 0 ... 0x1fff:
> @@ -1464,8 +1462,7 @@ static bool nested_svm_exit_handled_msr(struct vcpu_svm *svm)
>  	ret = msrpm[t1] & ((1 << param) << t0);
>  
>  out:
> -	nested_svm_unmap(nested_vmcb, KM_USER0);
> -	nested_svm_unmap(msrpm, KM_USER1);
> +	nested_svm_unmap(msrpm, KM_USER0);
>  
>  	return ret;
>  }
> -- 
> 1.6.0.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-09-04 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 14:51 [PATCH] Don't map nested_vmcb on INTERCEPT_MSR_PROT Alexander Graf
2009-09-03 16:00 ` Joerg Roedel
2009-09-04 17:05 ` Marcelo Tosatti [this message]
2009-09-04 22:59   ` Alexander Graf
2009-09-05  0:29     ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2009-09-03 14:12 Alexander Graf

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=20090904170521.GA6591@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=agraf@suse.de \
    --cc=joerg.roedel@amd.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.