From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM lock contention on 48 core AMD machine Date: Mon, 21 Mar 2011 11:50:36 +0200 Message-ID: <4D871F6C.40207@redhat.com> References: <20110318123031.GB6066@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Joerg Roedel , kvm@vger.kernel.org To: ben@iagu.net Return-path: Received: from mx1.redhat.com ([209.132.183.28]:5086 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751953Ab1CUJuy (ORCPT ); Mon, 21 Mar 2011 05:50:54 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 03/19/2011 06:45 AM, Ben Nagy wrote: > On Fri, Mar 18, 2011 at 7:30 PM, Joerg Roedel wrote: > > Hi Ben, > > > > Can you try to run > > > > # perf record -a -g > > > > for a while when your VMs are up and unresponsive? > > Hi Joerg, > > Thanks for the response. Here's that output: > > http://paste.ubuntu.com/582345/ > > Looks like it's spending all its time in kvm code, but there are some > symbols that are unresolved. Is the report still useful? > It's actually not kvm code, but timer code. Please build qemu with ./configure --disable-strip and redo. -- error compiling committee.c: too many arguments to function