mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH] KVM: async_pf: drop kvm_arch_async_page_present wrappers
Date: Tue, 21 Jan 2020 19:42:32 +0100	[thread overview]
Message-ID: <c2378317-6a8c-5a2e-aebe-e8d67b62bde3@de.ibm.com> (raw)
In-Reply-To: <1579614487-44583-2-git-send-email-pbonzini@redhat.com>



On 21.01.20 14:48, Paolo Bonzini wrote:
> The wrappers make it less clear that the position of the call
> to kvm_arch_async_page_present depends on the architecture, and
> that only one of the two call sites will actually be active.
> Remove them.
> 
> Cc: Andy Lutomirski <luto@kernel.org>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

looks sane. The binary code also looks identical.

Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>


> ---
>  virt/kvm/async_pf.c | 21 ++++-----------------
>  1 file changed, 4 insertions(+), 17 deletions(-)
> 
> diff --git a/virt/kvm/async_pf.c b/virt/kvm/async_pf.c
> index d8ef708a2ef6..15e5b037f92d 100644
> --- a/virt/kvm/async_pf.c
> +++ b/virt/kvm/async_pf.c
> @@ -17,21 +17,6 @@
>  #include "async_pf.h"
>  #include <trace/events/kvm.h>
>  
> -static inline void kvm_async_page_present_sync(struct kvm_vcpu *vcpu,
> -					       struct kvm_async_pf *work)
> -{
> -#ifdef CONFIG_KVM_ASYNC_PF_SYNC
> -	kvm_arch_async_page_present(vcpu, work);
> -#endif
> -}
> -static inline void kvm_async_page_present_async(struct kvm_vcpu *vcpu,
> -						struct kvm_async_pf *work)
> -{
> -#ifndef CONFIG_KVM_ASYNC_PF_SYNC
> -	kvm_arch_async_page_present(vcpu, work);
> -#endif
> -}
> -
>  static struct kmem_cache *async_pf_cache;
>  
>  int kvm_async_pf_init(void)
> @@ -80,7 +65,8 @@ static void async_pf_execute(struct work_struct *work)
>  	if (locked)
>  		up_read(&mm->mmap_sem);
>  
> -	kvm_async_page_present_sync(vcpu, apf);
> +	if (IS_ENABLED(CONFIG_KVM_ASYNC_PF_SYNC))
> +		kvm_arch_async_page_present(vcpu, apf);
>  
>  	spin_lock(&vcpu->async_pf.lock);
>  	list_add_tail(&apf->link, &vcpu->async_pf.done);
> @@ -157,7 +143,8 @@ void kvm_check_async_pf_completion(struct kvm_vcpu *vcpu)
>  		spin_unlock(&vcpu->async_pf.lock);
>  
>  		kvm_arch_async_page_ready(vcpu, work);
> -		kvm_async_page_present_async(vcpu, work);
> +		if (!IS_ENABLED(CONFIG_KVM_ASYNC_PF_SYNC))
> +			kvm_arch_async_page_present(vcpu, work);
>  
>  		list_del(&work->queue);
>  		vcpu->async_pf.queued--;
> 


  reply	other threads:[~2020-01-21 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 13:48 Paolo Bonzini
2020-01-21 18:42 ` Christian Borntraeger [this message]
2020-01-22  2:19 linmiaohe

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=c2378317-6a8c-5a2e-aebe-e8d67b62bde3@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=pbonzini@redhat.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®