From: Zachary Amsden <zamsden@redhat.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, kvm <kvm@vger.kernel.org>
Subject: Re: Bug in KVM clock backwards compensation
Date: Thu, 28 Apr 2011 12:06:53 -0700 [thread overview]
Message-ID: <4DB9BACD.2090609@redhat.com> (raw)
In-Reply-To: <20110428072209.GH20365@amd.com>
On 04/28/2011 12:22 AM, Roedel, Joerg wrote:
> On Thu, Apr 28, 2011 at 03:06:01AM -0400, Jan Kiszka wrote:
>
>> And /me still wonders (like I did when this first popped up) if the
>> proper place of determining TSC stability really have to be KVM.
>>
>> If the Linux core fails to detect some instability and KVM has to jump
>> in, shouldn't we better improve the core's detection abilities and make
>> use of them in KVM? Conceptually this looks like we are currently just
>> working around a core deficit in KVM.
>>
> Yes, good question. Has this ever triggered on a real machine (not
> counting the suspend/resume issue in)?
>
Yes... some platforms don't go haywire until you start using power
mangement, TSC is stable before that, but not afterwards, and depending
on the version of the kernel, KVM might detect this before the kernel does.
Honestly, the code is obsolete, but still useful for those who build KVM
as an external module on older kernels using the kvm-kmod system.
Zach
next prev parent reply other threads:[~2011-04-28 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 6:59 Bug in KVM clock backwards compensation Zachary Amsden
2011-04-28 7:06 ` Jan Kiszka
2011-04-28 7:22 ` Roedel, Joerg
2011-04-28 19:06 ` Zachary Amsden [this message]
2011-04-28 22:38 ` Jan Kiszka
2011-04-28 17:48 ` Zachary Amsden
2011-04-28 7:13 ` Roedel, Joerg
2011-04-28 18:34 ` Zachary Amsden
2011-04-28 20:20 ` Joerg Roedel
2011-04-29 3:00 ` Zachary Amsden
2011-04-29 8:40 ` Joerg Roedel
2011-04-29 18:17 ` Zachary Amsden
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=4DB9BACD.2090609@redhat.com \
--to=zamsden@redhat.com \
--cc=Joerg.Roedel@amd.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).