All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, agraf@suse.de,
	borntraeger@de.ibm.com, cornelia.huck@de.ibm.com,
	christoffer.dall@linaro.org, xiaoguangrong@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] KVM: Introduce kvm_arch_memslots_updated()
Date: Thu, 4 Jul 2013 12:53:15 +0300	[thread overview]
Message-ID: <20130704095315.GD5113@redhat.com> (raw)
In-Reply-To: <20130704134029.4db2736a.yoshikawa_takuya_b1@lab.ntt.co.jp>

On Thu, Jul 04, 2013 at 01:40:29PM +0900, Takuya Yoshikawa wrote:
> This is called right after the memslots is updated, i.e. when the result
> of update_memslots() gets installed in install_new_memslots().  Since
> the memslots needs to be updated twice when we delete or move a memslot,
> kvm_arch_commit_memory_region() does not correspond to this exactly.
> 
> In the following patch, x86 will use this new API to check if the mmio
> generation has reached its maximum value, in which case mmio sptes need
> to be flushed out.
> 
> Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
> ---
>  Removed the trailing space after "return old_memslots;" at this chance.
> 
>  arch/arm/kvm/arm.c         |    4 ++++
>  arch/ia64/kvm/kvm-ia64.c   |    4 ++++
>  arch/mips/kvm/kvm_mips.c   |    4 ++++
>  arch/powerpc/kvm/powerpc.c |    4 ++++
>  arch/s390/kvm/kvm-s390.c   |    4 ++++
>  arch/x86/kvm/x86.c         |    4 ++++
>  include/linux/kvm_host.h   |    1 +
>  virt/kvm/kvm_main.c        |    5 ++++-
>  8 files changed, 29 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
> index 327a1fb..51c3659 100644
> --- a/arch/arm/kvm/arm.c
> +++ b/arch/arm/kvm/arm.c
> @@ -219,6 +219,10 @@ long kvm_arch_dev_ioctl(struct file *filp,
>  	return -EINVAL;
>  }
>  
> +void kvm_arch_memslots_updated(struct kvm *kvm)
> +{
> +}
> +
>  int kvm_arch_prepare_memory_region(struct kvm *kvm,
>  				   struct kvm_memory_slot *memslot,
>  				   struct kvm_userspace_memory_region *mem,
> diff --git a/arch/ia64/kvm/kvm-ia64.c b/arch/ia64/kvm/kvm-ia64.c
> index 5b2dc0d..bdfd878 100644
> --- a/arch/ia64/kvm/kvm-ia64.c
> +++ b/arch/ia64/kvm/kvm-ia64.c
> @@ -1560,6 +1560,10 @@ int kvm_arch_create_memslot(struct kvm_memory_slot *slot, unsigned long npages)
>  	return 0;
>  }
>  
> +void kvm_arch_memslots_updated(struct kvm *kvm)
> +{
> +}
> +
>  int kvm_arch_prepare_memory_region(struct kvm *kvm,
>  		struct kvm_memory_slot *memslot,
>  		struct kvm_userspace_memory_region *mem,
> diff --git a/arch/mips/kvm/kvm_mips.c b/arch/mips/kvm/kvm_mips.c
> index e0dad02..daa32ea 100644
> --- a/arch/mips/kvm/kvm_mips.c
> +++ b/arch/mips/kvm/kvm_mips.c
> @@ -208,6 +208,10 @@ int kvm_arch_create_memslot(struct kvm_memory_slot *slot, unsigned long npages)
>  	return 0;
>  }
>  
> +void kvm_arch_memslots_updated(struct kvm *kvm)
> +{
> +}
> +
>  int kvm_arch_prepare_memory_region(struct kvm *kvm,
>                                  struct kvm_memory_slot *memslot,
>                                  struct kvm_userspace_memory_region *mem,
> diff --git a/arch/powerpc/kvm/powerpc.c b/arch/powerpc/kvm/powerpc.c
> index 6316ee3..ae63ae4 100644
> --- a/arch/powerpc/kvm/powerpc.c
> +++ b/arch/powerpc/kvm/powerpc.c
> @@ -420,6 +420,10 @@ int kvm_arch_create_memslot(struct kvm_memory_slot *slot, unsigned long npages)
>  	return kvmppc_core_create_memslot(slot, npages);
>  }
>  
> +void kvm_arch_memslots_updated(struct kvm *kvm)
> +{
> +}
> +
>  int kvm_arch_prepare_memory_region(struct kvm *kvm,
>  				   struct kvm_memory_slot *memslot,
>  				   struct kvm_userspace_memory_region *mem,
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index ba694d2..a3d797b 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -1056,6 +1056,10 @@ int kvm_arch_create_memslot(struct kvm_memory_slot *slot, unsigned long npages)
>  	return 0;
>  }
>  
> +void kvm_arch_memslots_updated(struct kvm *kvm)
> +{
> +}
> +
>  /* Section: memory related */
>  int kvm_arch_prepare_memory_region(struct kvm *kvm,
>  				   struct kvm_memory_slot *memslot,
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 7d71c0f..71912c9 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -7020,6 +7020,10 @@ out_free:
>  	return -ENOMEM;
>  }
>  
> +void kvm_arch_memslots_updated(struct kvm *kvm)
> +{
> +}
> +
>  int kvm_arch_prepare_memory_region(struct kvm *kvm,
>  				struct kvm_memory_slot *memslot,
>  				struct kvm_userspace_memory_region *mem,
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index e3aae6d..1c1e9de 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -498,6 +498,7 @@ int __kvm_set_memory_region(struct kvm *kvm,
>  void kvm_arch_free_memslot(struct kvm_memory_slot *free,
>  			   struct kvm_memory_slot *dont);
>  int kvm_arch_create_memslot(struct kvm_memory_slot *slot, unsigned long npages);
> +void kvm_arch_memslots_updated(struct kvm *kvm);
We can define empty function here like this:
#ifdef __KVM_HAVE_MEMSLOT_UPDATE
 void kvm_arch_memslots_updated(struct kvm *kvm);
#else
 static void kvm_arch_memslots_updated(struct kvm *kvm)
 {
 }
#endif

and make x86.c define __KVM_HAVE_MEMSLOT_UPDATE.

But I am fine with your approach too. Do other arch maintainers have any
preferences here?


>  int kvm_arch_prepare_memory_region(struct kvm *kvm,
>  				struct kvm_memory_slot *memslot,
>  				struct kvm_userspace_memory_region *mem,
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 1580dd4..4ed9d89 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -731,7 +731,10 @@ static struct kvm_memslots *install_new_memslots(struct kvm *kvm,
>  	update_memslots(slots, new, kvm->memslots->generation);
>  	rcu_assign_pointer(kvm->memslots, slots);
>  	synchronize_srcu_expedited(&kvm->srcu);
> -	return old_memslots; 
> +
> +	kvm_arch_memslots_updated(kvm);
> +
> +	return old_memslots;
>  }
>  
>  /*
> -- 
> 1.7.9.5

--
			Gleb.

  reply	other threads:[~2013-07-04  9:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  4:39 [PATCH 0/2] KVM: Introduce kvm_arch_memslots_updated() and use it for x86's mmio optimization Takuya Yoshikawa
2013-07-04  4:40 ` [PATCH 1/2] KVM: Introduce kvm_arch_memslots_updated() Takuya Yoshikawa
2013-07-04  9:53   ` Gleb Natapov [this message]
2013-07-04 10:24     ` Alexander Graf
2013-07-08 10:49     ` Cornelia Huck
2013-07-04 10:28   ` Xiao Guangrong
2013-07-04  4:41 ` [PATCH v2 2/2] KVM: x86: Avoid zapping mmio sptes twice for generation wraparound Takuya Yoshikawa
2013-07-04 10:27   ` 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=20130704095315.GD5113@redhat.com \
    --to=gleb@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    --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 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.