From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, guangrong.xiao@intel.com
Subject: Re: [PATCH] KVM: MTRR: Use default type for non-MTRR-covered gfn before WARN_ON
Date: Wed, 5 Aug 2015 11:58:32 +0200 [thread overview]
Message-ID: <55C1DE48.80705@redhat.com> (raw)
In-Reply-To: <20150804165639.26001.29833.stgit@gimli.home>
On 04/08/2015 18:58, Alex Williamson wrote:
> The patch was munged on commit to re-order these tests resulting in
> excessive warnings when trying to do device assignment. Return to
> original ordering: https://lkml.org/lkml/2015/7/15/769
>
> Fixes: 3e5d2fdceda1 ("KVM: MTRR: simplify kvm_mtrr_get_guest_memory_type")
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Applied, thanks. Sorry for the delay.
Paolo
> ---
>
> For v4.2
>
> arch/x86/kvm/mtrr.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kvm/mtrr.c b/arch/x86/kvm/mtrr.c
> index dc0a84a..9e8bf13 100644
> --- a/arch/x86/kvm/mtrr.c
> +++ b/arch/x86/kvm/mtrr.c
> @@ -672,16 +672,16 @@ u8 kvm_mtrr_get_guest_memory_type(struct kvm_vcpu *vcpu, gfn_t gfn)
> if (iter.mtrr_disabled)
> return mtrr_disabled_type();
>
> + /* not contained in any MTRRs. */
> + if (type == -1)
> + return mtrr_default_type(mtrr_state);
> +
> /*
> * We just check one page, partially covered by MTRRs is
> * impossible.
> */
> WARN_ON(iter.partial_map);
>
> - /* not contained in any MTRRs. */
> - if (type == -1)
> - return mtrr_default_type(mtrr_state);
> -
> return type;
> }
> EXPORT_SYMBOL_GPL(kvm_mtrr_get_guest_memory_type);
>
prev parent reply other threads:[~2015-08-05 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 16:58 [PATCH] KVM: MTRR: Use default type for non-MTRR-covered gfn before WARN_ON Alex Williamson
2015-08-05 2:22 ` Xiao Guangrong
2015-08-05 9:58 ` Paolo Bonzini [this message]
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=55C1DE48.80705@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=guangrong.xiao@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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 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).