public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Cc: gleb@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Avoid zapping mmio sptes twice for generation wraparound
Date: Wed, 03 Jul 2013 10:28:03 +0200	[thread overview]
Message-ID: <51D3E093.3020408@redhat.com> (raw)
In-Reply-To: <20130703171804.89d6cc2c.yoshikawa_takuya_b1@lab.ntt.co.jp>

Il 03/07/2013 10:18, Takuya Yoshikawa ha scritto:
> Since kvm_arch_prepare_memory_region() is called right after installing
> the slot marked invalid, wraparound checking should be there to avoid
> zapping mmio sptes when mmio generation is still MMIO_MAX_GEN - 1.
> 
> Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
> ---
>  This seems to be the simplest solution for fixing the off-by-one issue
>  we discussed before.
> 
>  arch/x86/kvm/mmu.c |    5 +----
>  arch/x86/kvm/x86.c |    7 +++++++
>  2 files changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 0d094da..bf7af1e 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -4383,11 +4383,8 @@ void kvm_mmu_invalidate_mmio_sptes(struct kvm *kvm)
>  	/*
>  	 * The very rare case: if the generation-number is round,
>  	 * zap all shadow pages.
> -	 *
> -	 * The max value is MMIO_MAX_GEN - 1 since it is not called
> -	 * when mark memslot invalid.
>  	 */
> -	if (unlikely(kvm_current_mmio_generation(kvm) >= (MMIO_MAX_GEN - 1))) {
> +	if (unlikely(kvm_current_mmio_generation(kvm) >= MMIO_MAX_GEN)) {
>  		printk_ratelimited(KERN_INFO "kvm: zapping shadow pages for mmio generation wraparound\n");
>  		kvm_mmu_invalidate_zap_all_pages(kvm);
>  	}
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 7d71c0f..9ddd4ff 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -7046,6 +7046,13 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm,
>  		memslot->userspace_addr = userspace_addr;
>  	}
>  
> +	/*
> +	 * In these cases, slots->generation has been increased for marking the
> +	 * slot invalid, so we need wraparound checking here.
> +	 */
> +	if ((change == KVM_MR_DELETE) || (change == KVM_MR_MOVE))
> +		kvm_mmu_invalidate_mmio_sptes(kvm);
> +
>  	return 0;
>  }
>  
> 

Applied, thanks.

Paolo

  reply	other threads:[~2013-07-03  8:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  8:18 [PATCH] KVM: x86: Avoid zapping mmio sptes twice for generation wraparound Takuya Yoshikawa
2013-07-03  8:28 ` Paolo Bonzini [this message]
2013-07-03  8:39   ` Xiao Guangrong
2013-07-03  8:50     ` Takuya Yoshikawa
2013-07-03  8:50       ` Xiao Guangrong
2013-07-03  8:50     ` Paolo Bonzini
2013-07-03  9:00       ` Xiao Guangrong
2013-07-03  8:50     ` Xiao Guangrong
2013-07-03  8:53       ` Gleb Natapov
2013-07-03  8:57         ` Paolo Bonzini
2013-07-03  9:03           ` Gleb Natapov
2013-07-03  8:53       ` Paolo Bonzini
2013-07-03  9:05         ` Takuya Yoshikawa
2013-07-03  9:05           ` Gleb Natapov
2013-07-03  9:08             ` Paolo Bonzini
2013-07-03  9:10               ` Gleb Natapov
2013-07-03  9:17                 ` Takuya Yoshikawa
2013-07-03  9: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=51D3E093.3020408@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=yoshikawa_takuya_b1@lab.ntt.co.jp \
    /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