All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris J Arges <chris.j.arges@canonical.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-unit-test failures
Date: Wed, 03 Sep 2014 19:52:28 +0200	[thread overview]
Message-ID: <5407555C.2010804@redhat.com> (raw)
In-Reply-To: <5407407F.3060500@canonical.com>

Il 03/09/2014 18:23, Chris J Arges ha scritto:
> $ uptime
>  16:18:31 up 53 min,  1 user,  load average: 1.16, 0.39, 0.17
> 
> $ grep -m1 model.name /proc/cpuinfo
> model name      : Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz
> 
> Here is the output of the command:
> qemu-system-x86_64 -enable-kvm -device pc-testdev -device
> isa-debug-exit,iobase=0xf4,iosize=0x4 -display none -serial stdio
> -device pci-testdev -kernel x86/kvmclock_test.flat -smp 2 --append
> 10000000 1409761075
> enabling apic
> enabling apic
> kvm-clock: cpu 0, msr 0x:44e520
> kvm-clock: cpu 0, msr 0x:44e520
> Wallclock test, threshold 5
> Seconds get from host:     1409761075
> Seconds get from kvmclock: 1409757927
> Offset:                    -3148
> offset too large!
> Wallclock test, threshold 5
> Seconds get from host:     1409761075
> Seconds get from kvmclock: 1409757927
> Offset:                    -3148
> offset too large!
> Check the stability of raw cycle ...
> Worst warp -3147762665310

I'm not sure about the reason for the warp, but indeed the offset and
uptime match (I'll check them against the trace tomorrow) so it's "just"
that the VM's TSC base is not taken into account correctly.

Can you gather another trace with the problematic patch reverted?

Paolo

  reply	other threads:[~2014-09-03 17:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 18:29 [PATCH 0/2] kvm-unit-tests: add check parameter to run_tests configuration Chris J Arges
2014-08-26 18:29 ` [PATCH 1/2] " Chris J Arges
2014-08-27 13:29   ` Paolo Bonzini
2014-08-27 14:42     ` [PATCH 1/2 v2] " Chris J Arges
2014-08-27 14:45     ` [PATCH 1/2 v3] " Chris J Arges
2014-08-27 14:52       ` Paolo Bonzini
2014-08-27 21:24         ` kvm-unit-test failures (was: [PATCH 1/2 v3] add check parameter to run_tests configuration) Chris J Arges
2014-08-27 22:05           ` Paolo Bonzini
2014-08-29 17:36             ` kvm-unit-test failures Chris J Arges
2014-08-29 21:05               ` Chris J Arges
2014-08-31 16:05                 ` Paolo Bonzini
2014-09-02 19:57                   ` Chris J Arges
2014-09-03 14:47                     ` Paolo Bonzini
2014-09-03 15:21                       ` Chris J Arges
2014-09-03 14:59                     ` Paolo Bonzini
2014-09-03 16:23                       ` Chris J Arges
2014-09-03 17:52                         ` Paolo Bonzini [this message]
2014-09-03 18:25                           ` Chris J Arges
     [not found]                             ` <54083688.6000201@redhat.com>
2014-09-04 11:33                               ` Paolo Bonzini
2014-09-04 12:24                                 ` Wanpeng Li
2014-09-04 13:11                                   ` Paolo Bonzini
2014-08-29 21:08               ` Paolo Bonzini
2014-08-29 21:18                 ` Chris J Arges
2014-08-26 18:29 ` [PATCH 2/2] x86/unittests.cfg: the pmu testcase requires that nmi_watchdog is disabled Chris J Arges
2014-08-27 13:29   ` Paolo Bonzini

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=5407555C.2010804@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=chris.j.arges@canonical.com \
    --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 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.