From: Paolo Bonzini <pbonzini@redhat.com>
To: Haozhong Zhang <haozhong.zhang@intel.com>,
kvm@vger.kernel.org, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, rkrcmar@redhat.com,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
ivan.d.cuevas.escareno@intel.com, karthik.kumar@intel.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Olif Chapman <olif.chapman@oracle.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v5 2/2] KVM: MMU: consider host cache mode in MMIO page check
Date: Fri, 15 Dec 2017 10:14:24 +0100 [thread overview]
Message-ID: <443f3841-51fa-4911-854a-7d1645d6d208@redhat.com> (raw)
In-Reply-To: <20171108075630.16991-3-haozhong.zhang@intel.com>
On 08/11/2017 08:56, 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 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>
WC should be allowed as well, because the combination of EPT_PAT=UC and
gPAT=WC gives WC effective memory type.
Maybe it's better after all if the lookup_memtype call remains in
kvm_is_mmio_pfn, like
if (!pfn_valid(pfn))
return true;
if (is_zero_pfn(pfn) || !PageReserved(pfn_to_page(pfn))
return false;
/* ... long comment ... */
if (!pat_enabled()
return true;
else {
cm = lookup_memtype(PFN_PHYS(pfn));
return cm == ...
}
or something like that.
Thanks,
Paolo
> ---
> arch/x86/kvm/mmu.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 0b481cc9c725..7715476bc5c9 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -2708,7 +2708,20 @@ 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));
> + return !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 in addition and
> + * only treat UC/UC- pages as MMIO.
> + */
> + (!pat_enabled() || pat_pfn_is_uc_or_uc_minus(pfn));
>
> return true;
> }
>
next prev parent reply other threads:[~2017-12-15 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 7:56 [PATCH v5 0/2] KVM: MMU: fix kvm_is_mmio_pfn() Haozhong Zhang
2017-11-08 7:56 ` [PATCH v5 1/2] x86/mm: add a function to check if a pfn is UC/UC- Haozhong Zhang
2017-11-15 10:44 ` David Hildenbrand
2017-11-16 7:08 ` Haozhong Zhang
2017-11-15 15:17 ` Dan Williams
2017-11-16 6:13 ` Haozhong Zhang
2017-12-18 12:55 ` Paolo Bonzini
2017-12-19 2:40 ` Haozhong Zhang
2017-12-19 10:42 ` Paolo Bonzini
2017-11-08 7:56 ` [PATCH v5 2/2] KVM: MMU: consider host cache mode in MMIO page check Haozhong Zhang
2017-12-15 9:14 ` Paolo Bonzini [this message]
2017-11-08 9:19 ` [PATCH v5 0/2] KVM: MMU: fix kvm_is_mmio_pfn() Xiao Guangrong
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=443f3841-51fa-4911-854a-7d1645d6d208@redhat.com \
--to=pbonzini@redhat.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=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpatocka@redhat.com \
--cc=olif.chapman@oracle.com \
--cc=rkrcmar@redhat.com \
--cc=x86@kernel.org \
--cc=xiaoguangrong.eric@gmail.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®