From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: pinning, tsc and apic Date: Thu, 15 May 2008 11:26:06 -0500 Message-ID: <20080515162606.GD29786@us.ibm.com> References: <20080512191923.GU17938@us.ibm.com> <20080514232506.GA18079@dmt> <482B7983.1030000@codemonkey.ws> <20080515065912.GE4017@sequoia.sous-sol.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti To: Chris Wright Return-path: Content-Disposition: inline In-Reply-To: <20080515065912.GE4017@sequoia.sous-sol.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org * Chris Wright [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/