All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 2/4] KVM: PPC: Book3S HV: Map single pages when doing dirty page logging
Date: Wed, 12 Dec 2018 05:18:00 +0000	[thread overview]
Message-ID: <1544591880.1865.2.camel@gmail.com> (raw)
In-Reply-To: <20181212041617.GC22265@blackberry>

On Wed, 2018-12-12 at 15:16 +1100, Paul Mackerras wrote:
> For radix guests, this makes KVM map guest memory as individual pages
> when dirty page logging is enabled for the memslot corresponding to
> the
> guest real address.  Having a separate partition-scoped PTE for each
> system page mapped to the guest means that we have a separate dirty
> bit for each page, thus making the reported dirty bitmap more
> accurate.
> Without this, if part of guest memory is backed by transparent huge
> pages, the dirty status is reported at a 2MB granularity rather than
> a 64kB (or 4kB) granularity for that part, causing userspace to have
> to transmit more data when migrating the guest.

Reviewed-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>

> 
> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
> ---
>  arch/powerpc/kvm/book3s_64_mmu_radix.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/powerpc/kvm/book3s_64_mmu_radix.c
> b/arch/powerpc/kvm/book3s_64_mmu_radix.c
> index d68162e..87ad35e 100644
> --- a/arch/powerpc/kvm/book3s_64_mmu_radix.c
> +++ b/arch/powerpc/kvm/book3s_64_mmu_radix.c
> @@ -683,6 +683,7 @@ int kvmppc_book3s_instantiate_page(struct
> kvm_vcpu *vcpu,
>  	pte_t pte, *ptep;
>  	unsigned int shift, level;
>  	int ret;
> +	bool large_enable;
>  
>  	/* used to check for invalidations in progress */
>  	mmu_seq = kvm->mmu_notifier_seq;
> @@ -732,12 +733,15 @@ int kvmppc_book3s_instantiate_page(struct
> kvm_vcpu *vcpu,
>  	pte = *ptep;
>  	local_irq_enable();
>  
> +	/* If we're logging dirty pages, always map single pages */
> +	large_enable = !(memslot->flags & KVM_MEM_LOG_DIRTY_PAGES);
> +
>  	/* Get pte level from shift/size */
> -	if (shift = PUD_SHIFT &&
> +	if (large_enable && shift = PUD_SHIFT &&
>  	    (gpa & (PUD_SIZE - PAGE_SIZE)) =
>  	    (hva & (PUD_SIZE - PAGE_SIZE))) {
>  		level = 2;
> -	} else if (shift = PMD_SHIFT &&
> +	} else if (large_enable && shift = PMD_SHIFT &&
>  		   (gpa & (PMD_SIZE - PAGE_SIZE)) =
>  		   (hva & (PMD_SIZE - PAGE_SIZE))) {
>  		level = 1;

  reply	other threads:[~2018-12-12  5:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  4:16 [PATCH 2/4] KVM: PPC: Book3S HV: Map single pages when doing dirty page logging Paul Mackerras
2018-12-12  5:18 ` Suraj Jitindar Singh [this message]
2018-12-12 23:29 ` David Gibson

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=1544591880.1865.2.camel@gmail.com \
    --to=sjitindarsingh@gmail.com \
    --cc=kvm-ppc@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.