All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@linaro.org>
To: "Longpeng(Mike)" <longpeng2@huawei.com>
Cc: kvm@vger.kernel.org, marc.zyngier@arm.com,
	linux-kernel@vger.kernel.org, wu.wubin@huawei.com,
	pbonzini@redhat.com, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm/arm64: KVM: clean up useless code in kvm_timer_enable
Date: Tue, 15 Nov 2016 12:41:51 +0100	[thread overview]
Message-ID: <20161115114151.GA3811@cbox> (raw)
In-Reply-To: <1478659814-364872-1-git-send-email-longpeng2@huawei.com>

On Wed, Nov 09, 2016 at 10:50:14AM +0800, Longpeng(Mike) wrote:
> 1) Since commit:41a54482 changed timer enabled variable to per-vcpu,
>    the correlative comment in kvm_timer_enable is useless now.
> 
> 2) After the kvm module init successfully, the timecounter is always
>    non-null, so we can remove the checking of timercounter.
> 
> Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>

Acked-by: Christoffer Dall <christoffer.dall@linaro.org>

> ---
>  virt/kvm/arm/arch_timer.c | 12 +-----------
>  1 file changed, 1 insertion(+), 11 deletions(-)
> 
> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> index 27a1f63..17b8fa5 100644
> --- a/virt/kvm/arm/arch_timer.c
> +++ b/virt/kvm/arm/arch_timer.c
> @@ -498,17 +498,7 @@ int kvm_timer_enable(struct kvm_vcpu *vcpu)
>  	if (ret)
>  		return ret;
>  
> -
> -	/*
> -	 * There is a potential race here between VCPUs starting for the first
> -	 * time, which may be enabling the timer multiple times.  That doesn't
> -	 * hurt though, because we're just setting a variable to the same
> -	 * variable that it already was.  The important thing is that all
> -	 * VCPUs have the enabled variable set, before entering the guest, if
> -	 * the arch timers are enabled.
> -	 */
> -	if (timecounter)
> -		timer->enabled = 1;
> +	timer->enabled = 1;
>  
>  	return 0;
>  }
> -- 
> 1.8.3.1
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/arm64: KVM: clean up useless code in kvm_timer_enable
Date: Tue, 15 Nov 2016 12:41:51 +0100	[thread overview]
Message-ID: <20161115114151.GA3811@cbox> (raw)
In-Reply-To: <1478659814-364872-1-git-send-email-longpeng2@huawei.com>

On Wed, Nov 09, 2016 at 10:50:14AM +0800, Longpeng(Mike) wrote:
> 1) Since commit:41a54482 changed timer enabled variable to per-vcpu,
>    the correlative comment in kvm_timer_enable is useless now.
> 
> 2) After the kvm module init successfully, the timecounter is always
>    non-null, so we can remove the checking of timercounter.
> 
> Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>

Acked-by: Christoffer Dall <christoffer.dall@linaro.org>

> ---
>  virt/kvm/arm/arch_timer.c | 12 +-----------
>  1 file changed, 1 insertion(+), 11 deletions(-)
> 
> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> index 27a1f63..17b8fa5 100644
> --- a/virt/kvm/arm/arch_timer.c
> +++ b/virt/kvm/arm/arch_timer.c
> @@ -498,17 +498,7 @@ int kvm_timer_enable(struct kvm_vcpu *vcpu)
>  	if (ret)
>  		return ret;
>  
> -
> -	/*
> -	 * There is a potential race here between VCPUs starting for the first
> -	 * time, which may be enabling the timer multiple times.  That doesn't
> -	 * hurt though, because we're just setting a variable to the same
> -	 * variable that it already was.  The important thing is that all
> -	 * VCPUs have the enabled variable set, before entering the guest, if
> -	 * the arch timers are enabled.
> -	 */
> -	if (timecounter)
> -		timer->enabled = 1;
> +	timer->enabled = 1;
>  
>  	return 0;
>  }
> -- 
> 1.8.3.1
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: "Longpeng(Mike)" <longpeng2@huawei.com>
Cc: marc.zyngier@arm.com, pbonzini@redhat.com, rkrcmar@redhat.com,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, zhaoshenglong@huawei.com,
	wu.wubin@huawei.com
Subject: Re: [PATCH] arm/arm64: KVM: clean up useless code in kvm_timer_enable
Date: Tue, 15 Nov 2016 12:41:51 +0100	[thread overview]
Message-ID: <20161115114151.GA3811@cbox> (raw)
In-Reply-To: <1478659814-364872-1-git-send-email-longpeng2@huawei.com>

On Wed, Nov 09, 2016 at 10:50:14AM +0800, Longpeng(Mike) wrote:
> 1) Since commit:41a54482 changed timer enabled variable to per-vcpu,
>    the correlative comment in kvm_timer_enable is useless now.
> 
> 2) After the kvm module init successfully, the timecounter is always
>    non-null, so we can remove the checking of timercounter.
> 
> Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>

Acked-by: Christoffer Dall <christoffer.dall@linaro.org>

> ---
>  virt/kvm/arm/arch_timer.c | 12 +-----------
>  1 file changed, 1 insertion(+), 11 deletions(-)
> 
> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> index 27a1f63..17b8fa5 100644
> --- a/virt/kvm/arm/arch_timer.c
> +++ b/virt/kvm/arm/arch_timer.c
> @@ -498,17 +498,7 @@ int kvm_timer_enable(struct kvm_vcpu *vcpu)
>  	if (ret)
>  		return ret;
>  
> -
> -	/*
> -	 * There is a potential race here between VCPUs starting for the first
> -	 * time, which may be enabling the timer multiple times.  That doesn't
> -	 * hurt though, because we're just setting a variable to the same
> -	 * variable that it already was.  The important thing is that all
> -	 * VCPUs have the enabled variable set, before entering the guest, if
> -	 * the arch timers are enabled.
> -	 */
> -	if (timecounter)
> -		timer->enabled = 1;
> +	timer->enabled = 1;
>  
>  	return 0;
>  }
> -- 
> 1.8.3.1
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-11-15 11:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09  2:50 [PATCH] arm/arm64: KVM: clean up useless code in kvm_timer_enable Longpeng(Mike)
2016-11-09  2:50 ` Longpeng(Mike)
2016-11-09  2:50 ` Longpeng(Mike)
2016-11-15 11:41 ` Christoffer Dall [this message]
2016-11-15 11:41   ` Christoffer Dall
2016-11-15 11:41   ` Christoffer Dall

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=20161115114151.GA3811@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longpeng2@huawei.com \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=wu.wubin@huawei.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 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.