public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@redhat.com>, Tomasz Chmielewski <mangoo@wpkg.org>,
	kvm@vger.kernel.org
Subject: Re: Houston, we have May 15, 1953 (says guest when host uses cpufreq, and dies)
Date: Thu, 19 Feb 2009 10:15:22 +0100	[thread overview]
Message-ID: <499D232A.7040206@redhat.com> (raw)
In-Reply-To: <499C7196.7050001@codemonkey.ws>

Anthony Liguori wrote:
> Are you suggesting that one should use cpufreq on a CPU without a
> constant tsc?  Isn't this just asking for trouble?

Depends on the (guest) clock source ;)

tsc isn't going to do well obviously.

kvmclock is designed to handle tsc frequency changes just fine.
And with the kvm-84 kernel module it actually works correctly.

HTH,
  Gerd



  reply	other threads:[~2009-02-19  9:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 14:51 Houston, we have May 15, 1953 (says guest when host uses cpufreq, and dies) Tomasz Chmielewski
2009-02-18 16:02 ` Anthony Liguori
2009-02-18 16:11   ` Tomasz Chmielewski
2009-02-18 16:59     ` Avi Kivity
2009-02-18 17:02       ` Tomasz Chmielewski
2009-02-18 20:37       ` Anthony Liguori
2009-02-19  9:15         ` Gerd Hoffmann [this message]
2009-02-19  9:20           ` Tomasz Chmielewski
2009-02-19 10:27             ` Gerd Hoffmann
2009-02-18 18:46 ` Marcelo Tosatti
2009-02-18 18:53   ` Tomasz Chmielewski
2009-02-18 18:57     ` Marcelo Tosatti
2009-02-18 19:07       ` Tomasz Chmielewski
2009-02-18 19:10         ` Marcelo Tosatti
2009-02-18 19:18           ` Tomasz Chmielewski
2009-02-18 19:32             ` Marcelo Tosatti
2009-02-18 20:02               ` Tomasz Chmielewski
2009-02-18 20:03                 ` Marcelo Tosatti
2009-02-19 14:43                   ` Tomasz Chmielewski
2009-03-07 14:59       ` Tomasz Chmielewski

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=499D232A.7040206@redhat.com \
    --to=kraxel@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mangoo@wpkg.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