From: Ryan Harper <ryanh@us.ibm.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: pinning, tsc and apic
Date: Thu, 15 May 2008 11:26:06 -0500 [thread overview]
Message-ID: <20080515162606.GD29786@us.ibm.com> (raw)
In-Reply-To: <20080515065912.GE4017@sequoia.sous-sol.org>
* Chris Wright <chrisw@sous-sol.org> [2008-05-15 02:01]:
> * Anthony Liguori (anthony@codemonkey.ws) wrote:
> > From a quick look, I suspect that the number of wildly off TSC
> > calibrations correspond to the VMs that are misbehaving. I think this
> > may mean that we have to re-examine the tsc delta computation.
> >
> > 10_serial.log:time.c: Detected 1995.038 MHz processor.
> > 11_serial.log:time.c: Detected 2363.195 MHz processor.
> > 12_serial.log:time.c: Detected 2492.675 MHz processor.
> > 13_serial.log:time.c: Detected 1995.061 MHz processor.
> > 14_serial.log:time.c: Detected 1994.917 MHz processor.
> > 15_serial.log:time.c: Detected 4100.735 MHz processor.
> > 16_serial.log:time.c: Detected 2075.800 MHz processor.
> > 17_serial.log:time.c: Detected 2674.350 MHz processor.
> > 18_serial.log:time.c: Detected 1995.002 MHz processor.
> > 19_serial.log:time.c: Detected 1994.978 MHz processor.
> > 1_serial.log:time.c: Detected 4384.310 MHz processor.
>
> Is this with pinning? We at least know we're losing small bits on
> migration. From my measurements it's ~3000 (outliers are 10-20k).
>
> Also, what happens if you roll back to kvm-userspace 7f5c4d15ece5?
I'll try that next.
>
> I'm using this:
>
On tip, using the patch, I still see hosed guests and tons of apic round
robin output, but the tsc calc seems to have stablized:
/tmp/10_serial.log:time.c: Detected 1995.018 MHz processor.
/tmp/11_serial.log:time.c: Detected 1995.009 MHz processor.
/tmp/12_serial.log:time.c: Detected 1995.012 MHz processor.
/tmp/13_serial.log:time.c: Detected 1995.013 MHz processor.
/tmp/14_serial.log:time.c: Detected 1995.016 MHz processor.
/tmp/15_serial.log:time.c: Detected 1995.020 MHz processor.
/tmp/16_serial.log:time.c: Detected 1995.020 MHz processor.
/tmp/18_serial.log:time.c: Detected 1995.020 MHz processor.
/tmp/19_serial.log:time.c: Detected 1995.023 MHz processor.
/tmp/1_serial.log:time.c: Detected 1995.008 MHz processor.
/tmp/20_serial.log:time.c: Detected 1995.011 MHz processor.
/tmp/21_serial.log:time.c: Detected 1995.016 MHz processor.
/tmp/22_serial.log:time.c: Detected 1995.016 MHz processor.
/tmp/23_serial.log:time.c: Detected 1995.013 MHz processor.
/tmp/24_serial.log:time.c: Detected 1995.018 MHz processor.
/tmp/25_serial.log:time.c: Detected 1995.030 MHz processor.
/tmp/26_serial.log:time.c: Detected 1995.021 MHz processor.
/tmp/27_serial.log:time.c: Detected 1995.026 MHz processor.
/tmp/28_serial.log:time.c: Detected 1995.016 MHz processor.
/tmp/29_serial.log:time.c: Detected 1995.012 MHz processor.
/tmp/2_serial.log:time.c: Detected 1995.020 MHz processor.
/tmp/30_serial.log:time.c: Detected 1995.021 MHz processor.
/tmp/31_serial.log:time.c: Detected 1995.021 MHz processor.
/tmp/32_serial.log:time.c: Detected 1995.008 MHz processor.
/tmp/33_serial.log:time.c: Detected 1995.015 MHz processor.
/tmp/34_serial.log:time.c: Detected 1995.018 MHz processor.
/tmp/35_serial.log:time.c: Detected 1995.017 MHz processor.
/tmp/36_serial.log:time.c: Detected 1995.013 MHz processor.
/tmp/37_serial.log:time.c: Detected 1995.003 MHz processor.
/tmp/38_serial.log:time.c: Detected 1995.036 MHz processor.
/tmp/39_serial.log:time.c: Detected 1995.020 MHz processor.
/tmp/3_serial.log:time.c: Detected 1995.017 MHz processor.
/tmp/40_serial.log:time.c: Detected 1994.998 MHz processor.
/tmp/41_serial.log:time.c: Detected 1995.015 MHz processor.
/tmp/43_serial.log:time.c: Detected 1995.007 MHz processor.
/tmp/44_serial.log:time.c: Detected 1995.029 MHz processor.
/tmp/45_serial.log:time.c: Detected 1995.009 MHz processor.
/tmp/46_serial.log:time.c: Detected 1995.025 MHz processor.
/tmp/47_serial.log:time.c: Detected 1995.019 MHz processor.
/tmp/48_serial.log:time.c: Detected 1995.013 MHz processor.
/tmp/4_serial.log:time.c: Detected 1995.024 MHz processor.
/tmp/5_serial.log:time.c: Detected 1995.016 MHz processor.
/tmp/6_serial.log:time.c: Detected 1995.023 MHz processor.
/tmp/7_serial.log:time.c: Detected 1995.036 MHz processor.
/tmp/8_serial.log:time.c: Detected 1995.013 MHz processor.
/tmp/9_serial.log:time.c: Detected 1995.014 MHz processor.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-05-15 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 19:19 pinning, tsc and apic Ryan Harper
2008-05-12 19:49 ` Anthony Liguori
2008-05-12 21:23 ` Ryan Harper
2008-05-12 21:44 ` Anthony Liguori
2008-05-13 18:56 ` Ryan Harper
2008-05-14 23:25 ` Marcelo Tosatti
2008-05-14 23:45 ` Anthony Liguori
2008-05-15 6:59 ` Chris Wright
2008-05-15 14:10 ` Anthony Liguori
2008-05-15 16:26 ` Ryan Harper [this message]
2008-06-18 13:12 ` [kvm-devel] " 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=20080515162606.GD29786@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=chrisw@sous-sol.org \
--cc=kvm-devel@lists.sourceforge.net \
--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.