From: Marcelo Tosatti <mtosatti@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, glommer@gmail.com
Subject: Re: [PATCH] KVM: remove useless write to vcpu->hv_clock.tsc_timestamp
Date: Wed, 15 Jan 2014 21:10:15 -0200 [thread overview]
Message-ID: <20140115231015.GA30432@amt.cnet> (raw)
In-Reply-To: <1389805691-3183-1-git-send-email-pbonzini@redhat.com>
On Wed, Jan 15, 2014 at 06:08:11PM +0100, Paolo Bonzini wrote:
> After the previous patch from Marcelo, the comment before this write
> became obsolete. In fact, the write is unnecessary. The calls to
> kvm_write_tsc ultimately result in a master clock update as soon as
> all TSCs agree and the master clock is re-enabled. This master
> clock update will rewrite tsc_timestamp.
>
> So, together with the comment, delete the dead write too.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> arch/x86/kvm/x86.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 842abd3..0fbdced 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -1278,8 +1278,6 @@ void kvm_write_tsc(struct kvm_vcpu *vcpu, struct msr_data *msr)
> kvm->arch.last_tsc_write = data;
> kvm->arch.last_tsc_khz = vcpu->arch.virtual_tsc_khz;
>
> - /* Reset of TSC must disable overshoot protection below */
> - vcpu->arch.hv_clock.tsc_timestamp = 0;
> vcpu->arch.last_guest_tsc = data;
>
> /* Keep track of which generation this VCPU has synchronized to */
> --
> 1.7.1
Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
prev parent reply other threads:[~2014-01-15 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 17:08 [PATCH] KVM: remove useless write to vcpu->hv_clock.tsc_timestamp Paolo Bonzini
2014-01-15 23:10 ` Marcelo Tosatti [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=20140115231015.GA30432@amt.cnet \
--to=mtosatti@redhat.com \
--cc=glommer@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.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