public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Remove user_alloc from struct kvm_memory_slot
Date: Mon, 11 Feb 2013 11:52:14 +0200	[thread overview]
Message-ID: <20130211095214.GW7837@redhat.com> (raw)
In-Reply-To: <20130207185557.b32ba396.yoshikawa_takuya_b1@lab.ntt.co.jp>

On Thu, Feb 07, 2013 at 06:55:57PM +0900, Takuya Yoshikawa wrote:
> This field was needed to differentiate memory slots created by the new
> API, KVM_SET_USER_MEMORY_REGION, from those by the old equivalent,
> KVM_SET_MEMORY_REGION, whose support was dropped long before:
> 
>   commit b74a07beed0e64bfba413dcb70dd6749c57f43dc
>   KVM: Remove kernel-allocated memory regions
> 
> Although we also have private memory slots to which KVM allocates
> memory with vm_mmap(), !user_alloc slots in other words, the slot id
> should be enough for differentiating them.
> 
> Note: corresponding function parameters will be removed later.
> 
Applied. Thanks.

> Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
> ---
>  arch/x86/kvm/x86.c       |   37 ++++++++++++++++---------------------
>  include/linux/kvm_host.h |    1 -
>  virt/kvm/kvm_main.c      |    1 -
>  3 files changed, 16 insertions(+), 23 deletions(-)
> 
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 373e17a..3c5bb6f 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -6897,33 +6897,28 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm,
>  				bool user_alloc)
>  {
>  	int npages = memslot->npages;
> -	int map_flags = MAP_PRIVATE | MAP_ANONYMOUS;
>  
> -	/* Prevent internal slot pages from being moved by fork()/COW. */
> -	if (memslot->id >= KVM_USER_MEM_SLOTS)
> -		map_flags = MAP_SHARED | MAP_ANONYMOUS;
> -
> -	/*To keep backward compatibility with older userspace,
> -	 *x86 needs to handle !user_alloc case.
> +	/*
> +	 * Only private memory slots need to be mapped here since
> +	 * KVM_SET_MEMORY_REGION ioctl is no longer supported.
>  	 */
> -	if (!user_alloc) {
> -		if (npages && !old.npages) {
> -			unsigned long userspace_addr;
> +	if ((memslot->id >= KVM_USER_MEM_SLOTS) && npages && !old.npages) {
> +		unsigned long userspace_addr;
>  
> -			userspace_addr = vm_mmap(NULL, 0,
> -						 npages * PAGE_SIZE,
> -						 PROT_READ | PROT_WRITE,
> -						 map_flags,
> -						 0);
> +		/*
> +		 * MAP_SHARED to prevent internal slot pages from being moved
> +		 * by fork()/COW.
> +		 */
> +		userspace_addr = vm_mmap(NULL, 0, npages * PAGE_SIZE,
> +					 PROT_READ | PROT_WRITE,
> +					 MAP_SHARED | MAP_ANONYMOUS, 0);
>  
> -			if (IS_ERR((void *)userspace_addr))
> -				return PTR_ERR((void *)userspace_addr);
> +		if (IS_ERR((void *)userspace_addr))
> +			return PTR_ERR((void *)userspace_addr);
>  
> -			memslot->userspace_addr = userspace_addr;
> -		}
> +		memslot->userspace_addr = userspace_addr;
>  	}
>  
> -
>  	return 0;
>  }
>  
> @@ -6935,7 +6930,7 @@ void kvm_arch_commit_memory_region(struct kvm *kvm,
>  
>  	int nr_mmu_pages = 0, npages = mem->memory_size >> PAGE_SHIFT;
>  
> -	if (!user_alloc && !old.user_alloc && old.npages && !npages) {
> +	if ((mem->slot >= KVM_USER_MEM_SLOTS) && old.npages && !npages) {
>  		int ret;
>  
>  		ret = vm_munmap(old.userspace_addr,
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index 0350e0d..722cae7 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -273,7 +273,6 @@ struct kvm_memory_slot {
>  	unsigned long userspace_addr;
>  	u32 flags;
>  	short id;
> -	bool user_alloc;
>  };
>  
>  static inline unsigned long kvm_dirty_bitmap_bytes(struct kvm_memory_slot *memslot)
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 2e93630..adc68fe 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -839,7 +839,6 @@ int __kvm_set_memory_region(struct kvm *kvm,
>  
>  	r = -ENOMEM;
>  	if (change == KVM_MR_CREATE) {
> -		new.user_alloc = user_alloc;
>  		new.userspace_addr = mem->userspace_addr;
>  
>  		if (kvm_arch_create_memslot(&new, npages))
> -- 
> 1.7.5.4

--
			Gleb.

      parent reply	other threads:[~2013-02-11  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07  9:55 [PATCH] KVM: Remove user_alloc from struct kvm_memory_slot Takuya Yoshikawa
2013-02-08 23:32 ` Marcelo Tosatti
2013-02-11  9:52 ` Gleb Natapov [this message]

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=20130211095214.GW7837@redhat.com \
    --to=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox