linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiao Guangrong <xiaoguangrong.eric@gmail.com>
To: Haozhong Zhang <haozhong.zhang@intel.com>,
	kvm@vger.kernel.org, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	rkrcmar@redhat.com, Dan Williams <dan.j.williams@intel.com>,
	ivan.d.cuevas.escareno@intel.com, karthik.kumar@intel.com,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v2 2/2] KVM: MMU: consider host cache mode in MMIO page check
Date: Thu, 2 Nov 2017 15:56:31 +0800	[thread overview]
Message-ID: <824e2162-a6f0-9ca3-e45c-2dbf09a01f1a@gmail.com> (raw)
In-Reply-To: <20171031114840.12615-3-haozhong.zhang@intel.com>



On 10/31/2017 07:48 PM, Haozhong Zhang wrote:
> Some reserved pages, such as those from NVDIMM DAX devices, are
> not for MMIO, and can be mapped with cached memory type for better
> performance. However, the above check misconceives those pages as
> MMIO.  Because KVM maps MMIO pages with UC memory type, the
> performance of guest accesses to those pages would be harmed.
> Therefore, we check the host memory type by lookup_memtype() in
> addition and only treat UC/UC- pages as MMIO.
> 
> Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> Reported-by: Cuevas Escareno, Ivan D <ivan.d.cuevas.escareno@intel.com>
> Reported-by: Kumar, Karthik <karthik.kumar@intel.com>
> ---
>   arch/x86/kvm/mmu.c | 30 +++++++++++++++++++++++++++---
>   1 file changed, 27 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 0b481cc9c725..206828d18857 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -2707,10 +2707,34 @@ static bool mmu_need_write_protect(struct kvm_vcpu *vcpu, gfn_t gfn,
>   
>   static bool kvm_is_mmio_pfn(kvm_pfn_t pfn)
>   {
> -	if (pfn_valid(pfn))
> -		return !is_zero_pfn(pfn) && PageReserved(pfn_to_page(pfn));
> +	bool is_mmio = true;
>   
> -	return true;
> +	if (pfn_valid(pfn)) {
> +		is_mmio = !is_zero_pfn(pfn) && PageReserved(pfn_to_page(pfn));
> +
> +		/*
> +		 * Some reserved pages, such as those from NVDIMM DAX
> +		 * devices, are not for MMIO, and can be mapped with
> +		 * cached memory type for better performance. However,
> +		 * the above check misconceives those pages as MMIO.
> +		 * Because KVM maps MMIO pages with UC memory type,
> +		 * the performance of guest accesses to those pages
> +		 * would be harmed. Therefore, we check the host
> +		 * memory type by lookup_memtype() in addition and
> +		 * only treat UC/UC- pages as MMIO.
> +		 *
> +		 * lookup_memtype() works only when PAT is enabled, so
> +		 * add pat_enabled() check here.
> +		 */
> +		if (is_mmio && pat_enabled()) {
> +			enum page_cache_mode cm = lookup_memtype(PFN_PHYS(pfn));
> +
> +			is_mmio = (cm == _PAGE_CACHE_MODE_UC ||
> +				   cm == _PAGE_CACHE_MODE_UC_MINUS);
> +		}
> +	}

You can move all of these detailed stuffs to pat.c and abstract them by introducing
a function, maybe named pat_pfn_is_uc(). I think this is what Ingo wants.

  reply	other threads:[~2017-11-02  7:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 11:48 [PATCH v2 0/2] KVM: MMU: fix kvm_is_mmio_pfn() Haozhong Zhang
2017-10-31 11:48 ` [PATCH v2 1/2] x86/mm: expose lookup_memtype() Haozhong Zhang
2017-10-31 11:48 ` [PATCH v2 2/2] KVM: MMU: consider host cache mode in MMIO page check Haozhong Zhang
2017-11-02  7:56   ` Xiao Guangrong [this message]
2017-11-02  9:20     ` Haozhong Zhang
2017-11-02  6:48 ` [PATCH v2 0/2] KVM: MMU: fix kvm_is_mmio_pfn() Haozhong Zhang
2017-11-02 17:37 ` Konrad Rzeszutek Wilk
2017-11-03  0:26   ` Haozhong Zhang
2017-11-03 14:15 ` Mikulas Patocka
2017-11-08  1:30   ` Haozhong Zhang
2017-11-08 12:24     ` Mikulas Patocka

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=824e2162-a6f0-9ca3-e45c-2dbf09a01f1a@gmail.com \
    --to=xiaoguangrong.eric@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=haozhong.zhang@intel.com \
    --cc=ivan.d.cuevas.escareno@intel.com \
    --cc=karthik.kumar@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=x86@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).