All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org,
	Benjamin Serebrin <benjamin.serebrin@amd.com>
Subject: Re: [patch 0/3] synchronized TSC between vcpu's on SMP guests
Date: Wed, 10 Dec 2008 01:48:34 +0300	[thread overview]
Message-ID: <493EF5C2.3060603@msgid.tls.msk.ru> (raw)
In-Reply-To: <20081209104744.GA8611@dmt.cnet>

Marcelo Tosatti wrote:
> On Tue, Dec 09, 2008 at 02:38:08PM +0300, Michael Tokarev wrote:
>> Marcelo Tosatti wrote:
>>> Most Intel hosts are supposed to have their TSC's synchronized. This
>>> patchset attempts to fix the sites which overwrite the TSC making them
>>> appear unsynchronized to the guest.
>> By the way, phenoms are also supposed to have synced TSCs, at least
>> the host reports TSC syncronization works.  But guests still thinks
>> TSC is unstable, even on uniprocessor guests using kvm_clock...
> 
> On uniprocessor guests? Perhaps, if the guest uses the vmmouse for
> example. In such case, is the TSC reported unstable right after boot?

Hm.  I see "TSC unsyncronized" messages on a bare linux-2.6.27 guests,
without anything but virtio_{blk,net} loaded.  "Uniprocessor guests" -
I mean, a guest that has only one CPU, not necessary kernel that only
supports one CPU.

Here are some lines from dmesg when booting a guest
on a phenom machine:

Dec  4 19:17:42 iserv kernel: kvm-clock: cpu 0, msr 0:3d0801, boot clock

Dec  4 19:17:42 iserv kernel: SMP: Allowing 8 CPUs, 7 hotplug CPUs

Dec  4 19:17:42 iserv kernel: NR_CPUS: 8, nr_cpu_ids: 8, nr_node_ids 1
Dec  4 19:17:42 iserv kernel: kvm-clock: cpu 0, msr 0:180b801, primary cpu clock

Dec  4 19:17:42 iserv kernel: TSC: Unable to calibrate against PIT
Dec  4 19:17:42 iserv kernel: TSC: using PMTIMER reference calibration

Dec  4 19:17:42 iserv kernel: SMP alternatives: switching to UP code

Dec  4 19:17:42 iserv kernel: Booting paravirtualized kernel on KVM

Dec  4 19:17:42 iserv kernel: Processing INITRAMFS
Dec  4 19:17:42 iserv kernel: loading module virtio_pci

Dec  4 19:17:42 iserv kernel: EXT3 FS on vda, internal journal

Dec  4 19:26:24 iserv kernel: Clocksource tsc unstable (delta = -126732353 ns)

(Note the time difference between last and all previous lines.

At this time, there are only 5 user processes running.  Like this:

    1 ?        Ss     0:04 init [2]
  791 ?        Ss     0:00 /sbin/syslogd
  800 ?        Ss     0:00 /sbin/klogd -x
  845 ?        Ss     0:00 /usr/sbin/unbound
 6423 tty1     Ss+    0:00 /sbin/getty 38400 tty1

(it's not real example but close).

Linux iserv 2.6.27-i686smp #2.6.27.7 SMP Fri Nov 21 13:24:19 MSK 2008 i686 GNU/Linux
kvm-79.

Thanks!

/mjt

  reply	other threads:[~2008-12-09 22:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09  1:12 [patch 0/3] synchronized TSC between vcpu's on SMP guests Marcelo Tosatti
2008-12-09  1:12 ` [patch 1/3] QEMU/KVM: x86: separate TSC load from kvm_arch_load_regs Marcelo Tosatti
2008-12-10 10:10   ` Avi Kivity
2008-12-09  1:12 ` [patch 2/3] QEMU/KVM: BIOS: revert TSC zeroing Marcelo Tosatti
2008-12-09  1:12 ` [patch 3/3] KVM: VMX: initialize TSC offset relative to vm creation time Marcelo Tosatti
2008-12-10 10:19   ` Avi Kivity
2008-12-10 16:53     ` Marcelo Tosatti
2008-12-11 17:38       ` Avi Kivity
2008-12-11 19:45         ` Marcelo Tosatti
2008-12-28  9:26           ` Avi Kivity
2008-12-09 11:38 ` [patch 0/3] synchronized TSC between vcpu's on SMP guests Michael Tokarev
2008-12-09 10:47   ` Marcelo Tosatti
2008-12-09 22:48     ` Michael Tokarev [this message]
2008-12-22 23:16 ` David S. Ahern
2008-12-28  9:33 ` Avi Kivity

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=493EF5C2.3060603@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=avi@redhat.com \
    --cc=benjamin.serebrin@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.