public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: pbonzini@redhat.com, gleb@kernel.org, mtosatti@redhat.com,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	bsd@redhat.com, lersek@redhat.com, jordan.l.justen@intel.com,
	edk2-devel@lists.sourceforge.net,
	Xiao Guangrong <guangrong.xiao@intel.com>
Subject: Re: [PATCH 1/3] KVM: MTRR: fix memory type handling if MTRR is completely disabled
Date: Wed, 15 Jul 2015 22:10:18 -0600	[thread overview]
Message-ID: <1437019818.1391.544.camel@redhat.com> (raw)
In-Reply-To: <1436988356-4565-1-git-send-email-guangrong.xiao@linux.intel.com>

On Thu, 2015-07-16 at 03:25 +0800, Xiao Guangrong wrote:
> From: Xiao Guangrong <guangrong.xiao@intel.com>
> 
> Currently code uses default memory type if MTRR is fully disabled,
> fix it by using UC instead
> 
> Signed-off-by: Xiao Guangrong <guangrong.xiao@intel.com>
> ---

Seems to work for me.  I don't see a 0th patch, but for the series:

Tested-by: Alex Williamson <alex.williamson@redhat.com>

Thanks!

>  arch/x86/kvm/mtrr.c | 21 ++++++++++++++++++++-
>  1 file changed, 20 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kvm/mtrr.c b/arch/x86/kvm/mtrr.c
> index de1d2d8..e275013 100644
> --- a/arch/x86/kvm/mtrr.c
> +++ b/arch/x86/kvm/mtrr.c
> @@ -120,6 +120,16 @@ static u8 mtrr_default_type(struct kvm_mtrr *mtrr_state)
>  	return mtrr_state->deftype & IA32_MTRR_DEF_TYPE_TYPE_MASK;
>  }
>  
> +static u8 mtrr_disabled_type(void)
> +{
> +	/*
> +	 * Intel SDM 11.11.2.2: all MTRRs are disabled when
> +	 * IA32_MTRR_DEF_TYPE.E bit is cleared, and the UC
> +	 * memory type is applied to all of physical memory.
> +	 */
> +	return MTRR_TYPE_UNCACHABLE;
> +}
> +
>  /*
>  * Three terms are used in the following code:
>  * - segment, it indicates the address segments covered by fixed MTRRs.
> @@ -434,6 +444,8 @@ struct mtrr_iter {
>  
>  	/* output fields. */
>  	int mem_type;
> +	/* mtrr is completely disabled? */
> +	bool mtrr_disabled;
>  	/* [start, end) is not fully covered in MTRRs? */
>  	bool partial_map;
>  
> @@ -549,7 +561,7 @@ static void mtrr_lookup_var_next(struct mtrr_iter *iter)
>  static void mtrr_lookup_start(struct mtrr_iter *iter)
>  {
>  	if (!mtrr_is_enabled(iter->mtrr_state)) {
> -		iter->partial_map = true;
> +		iter->mtrr_disabled = true;
>  		return;
>  	}
>  
> @@ -563,6 +575,7 @@ static void mtrr_lookup_init(struct mtrr_iter *iter,
>  	iter->mtrr_state = mtrr_state;
>  	iter->start = start;
>  	iter->end = end;
> +	iter->mtrr_disabled = false;
>  	iter->partial_map = false;
>  	iter->fixed = false;
>  	iter->range = NULL;
> @@ -656,6 +669,9 @@ u8 kvm_mtrr_get_guest_memory_type(struct kvm_vcpu *vcpu, gfn_t gfn)
>  		return MTRR_TYPE_WRBACK;
>  	}
>  
> +	if (iter.mtrr_disabled)
> +		return mtrr_disabled_type();
> +
>  	/* It is not covered by MTRRs. */
>  	if (iter.partial_map) {
>  		/*
> @@ -689,6 +705,9 @@ bool kvm_mtrr_check_gfn_range_consistency(struct kvm_vcpu *vcpu, gfn_t gfn,
>  			return false;
>  	}
>  
> +	if (iter.mtrr_disabled)
> +		return true;
> +
>  	if (!iter.partial_map)
>  		return true;
>  




  parent reply	other threads:[~2015-07-16  4:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 19:25 [PATCH 1/3] KVM: MTRR: fix memory type handling if MTRR is completely disabled Xiao Guangrong
2015-07-15 19:25 ` [PATCH 2/3] KVM: MTRR: simplify kvm_mtrr_get_guest_memory_type Xiao Guangrong
2015-07-29 19:07   ` Alex Williamson
2015-07-30  7:21     ` [edk2] " Paolo Bonzini
2015-07-15 19:25 ` [PATCH 3/3] KVM: x86: quirkily apply WB to all memory if cache is disabled Xiao Guangrong
2015-07-23  5:56   ` Paolo Bonzini
2015-07-23  6:03     ` Xiao Guangrong
2015-07-16  4:10 ` Alex Williamson [this message]
2015-07-23  6:21   ` [PATCH 1/3] KVM: MTRR: fix memory type handling if MTRR is completely disabled Paolo Bonzini
2015-07-23  6:29     ` Xiao Guangrong
2015-07-23  7:18       ` 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=1437019818.1391.544.camel@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=bsd@redhat.com \
    --cc=edk2-devel@lists.sourceforge.net \
    --cc=gleb@kernel.org \
    --cc=guangrong.xiao@intel.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=jordan.l.justen@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=lersek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@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