From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: KVM: x86: workaround SuSE's 2.6.16 pvclock vs masterclock issue
Date: Thu, 22 Jan 2015 20:33:31 +0100 [thread overview]
Message-ID: <20150122193327.GA6543@potion.brq.redhat.com> (raw)
In-Reply-To: <20150122181253.GA6957@amt.cnet>
2015-01-22 16:12-0200, Marcelo Tosatti:
> On Thu, Jan 22, 2015 at 02:59:28PM +0100, Radim Krčmář wrote:
> > I don't understand what the guest wants to achieve with the delta.
>
> Neither do I. It seems to assume that TSC delta is unreliable, while
> system_timestamp is reliable.
>
> Therefore if TSC delta is large, request a system_timestamp update,
> which keeps TSC delta small.
I was wondering how they do that ... kvm clock has like 1 MSR interface;
multiple registrations are supposed to work?
> > I thought that checking this only made sense if the guest didn't believe
> > that PV clock works with large delta. And they only want precision.
> > (What else is there on a clock?)
>
> Ok right they assumed TSC was not reliable?
Most likely. (And that doing complicated magic is going to help it --
doesn't VMENTRY do pretty much everyting that can be done with
unreliable TSC?)
next prev parent reply other threads:[~2015-01-22 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 17:54 KVM: x86: workaround SuSE's 2.6.16 pvclock vs masterclock issue Marcelo Tosatti
2015-01-20 19:40 ` Paolo Bonzini
2015-01-21 14:09 ` Radim Krčmář
2015-01-21 14:16 ` Marcelo Tosatti
2015-01-21 17:00 ` Radim Krčmář
2015-01-22 1:40 ` Marcelo Tosatti
2015-01-22 13:59 ` Radim Krčmář
2015-01-22 18:12 ` Marcelo Tosatti
2015-01-22 19:33 ` Radim Krčmář [this message]
2015-01-22 8:10 ` Paolo Bonzini
2015-01-22 17:02 ` Radim Krčmář
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=20150122193327.GA6543@potion.brq.redhat.com \
--to=rkrcmar@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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