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 16:47:12 +0200 [thread overview]
Message-ID: <540729F0.20006@redhat.com> (raw)
In-Reply-To: <54062146.9040609@canonical.com>
Il 02/09/2014 21:57, Chris J Arges ha scritto:
>> > Can you please trace the test using trace-cmd
>> > (http://www.linux-kvm.org/page/Tracing) and send the output?
>> >
>> > Paolo
>> >
> Paolo,
>
> I have posted the trace data here:
> http://people.canonical.com/~arges/kvm/trace.dat.xz
Can you try running the test again (no need to get a new trace) with
clocksource=hpet on the kernel command line?
Paolo
next prev parent reply other threads:[~2014-09-03 14:47 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 [this message]
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
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=540729F0.20006@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.