linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] Guest kernel hangs in smp kvm for older kernels	prior to tsc sync cleanup
Date: Wed, 19 Dec 2007 17:21:06 +0200	[thread overview]
Message-ID: <476936E2.9010902@qumranet.com> (raw)
In-Reply-To: <20071219150938.GA15267@elte.hu>

Ingo Molnar wrote:
> try this test perhaps in an SMP guest:
>
>  http://people.redhat.com/mingo/time-warp-test/time-warp-test.c
>
> you can ignore TSC warps - but no GTOD or CLOCK warps should occur.
>
>   

On a broken guest kernel, I see gtod and clock warps.  On a good guest 
kernel, I do not, presumably because the tsc clocksource is marked as 
unstable.

I see tsc warps on both.  8 threads on 4 cpus.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2007-12-19 15:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 17:20 Guest kernel hangs in smp kvm for older kernels prior to tsc sync cleanup Avi Kivity
2007-12-18 22:19 ` Ingo Molnar
2007-12-19  6:33   ` Avi Kivity
2007-12-19 11:19     ` [kvm-devel] " Avi Kivity
2007-12-19 11:39       ` Avi Kivity
2007-12-19 14:06         ` Ingo Molnar
2007-12-19 14:27           ` Avi Kivity
2007-12-19 15:32             ` Glauber de Oliveira Costa
2007-12-19 15:41               ` Avi Kivity
2007-12-20 10:34                 ` Glauber de Oliveira Costa
2007-12-19 16:55               ` Amit Shah
2007-12-19 17:04                 ` [kvm-devel] Guest kernel hangs in smp kvm for older kernelsprior " Dor Laor
2007-12-19 17:09                   ` Avi Kivity
2007-12-19 14:53           ` [kvm-devel] Guest kernel hangs in smp kvm for older kernels prior " Avi Kivity
2007-12-19 15:09             ` Ingo Molnar
2007-12-19 15:21               ` Avi Kivity [this message]

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=476936E2.9010902@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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).