From: Marcelo Tosatti <mtosatti@redhat.com>
To: Tomasz Grabiec <tgrabiec@cloudius-systems.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: fix TSC matching
Date: Fri, 15 Aug 2014 13:54:17 -0300 [thread overview]
Message-ID: <20140815165417.GA29279@amt.cnet> (raw)
In-Reply-To: <1403595763-2751-1-git-send-email-tgrabiec@cloudius-systems.com>
Ping on integration.
On Tue, Jun 24, 2014 at 09:42:43AM +0200, Tomasz Grabiec wrote:
> I've observed kvmclock being marked as unstable on a modern
> single-socket system with a stable TSC and qemu-1.6.2 or qemu-2.0.0.
>
> The culprit was failure in TSC matching because of overflow of
> kvm_arch::nr_vcpus_matched_tsc in case there were multiple TSC writes
> in a single synchronization cycle.
next prev parent reply other threads:[~2014-08-15 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 7:42 [PATCH] KVM: x86: fix TSC matching Tomasz Grabiec
2014-06-30 8:43 ` Tomasz Grabiec
2014-06-30 11:41 ` Paolo Bonzini
2014-06-30 17:45 ` Marcelo Tosatti
2014-08-15 16:54 ` Marcelo Tosatti [this message]
2014-08-17 8:54 ` Paolo Bonzini
2014-08-26 9:08 ` Pekka Enberg
2014-08-26 11:43 ` Paolo Bonzini
2014-09-03 19:02 ` Marcelo Tosatti
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=20140815165417.GA29279@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=tgrabiec@cloudius-systems.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