From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48418) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEJC2-0006hY-Kb for qemu-devel@nongnu.org; Tue, 27 Aug 2013 09:20:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VEJBw-0004qT-HU for qemu-devel@nongnu.org; Tue, 27 Aug 2013 09:20:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54293) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEJBw-0004qJ-AL for qemu-devel@nongnu.org; Tue, 27 Aug 2013 09:20:16 -0400 Date: Tue, 27 Aug 2013 16:20:09 +0300 From: Gleb Natapov Message-ID: <20130827132008.GB29072@redhat.com> References: <20130813181713.GA5204@irqsave.net> <20130826124031.GB22977@redhat.com> <20130826124941.GA5418@irqsave.net> <20130826143320.GA22899@redhat.com> <20130826164526.GB5418@irqsave.net> <20130826204729.GW2631@otherpad.lan.raisama.net> <20130827131816.GA5436@irqsave.net> <20130827131756.GA29072@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20130827131756.GA29072@redhat.com> Subject: Re: [Qemu-devel] KVM guest cpu L3 cache and cpufreq List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?utf-8?Q?Beno=C3=AEt?= Canet Cc: pbonzini@redhat.com, Igor Mammedov , Eduardo Habkost , Andreas =?utf-8?Q?F=C3=A4rber?= , qemu-devel@nongnu.org On Tue, Aug 27, 2013 at 04:17:56PM +0300, Gleb Natapov wrote: > On Tue, Aug 27, 2013 at 03:18:16PM +0200, Beno=C3=AEt Canet wrote: > >=20 > > Hello Eduardo, > >=20 > > I read a bit about caches on wikipedia. > >=20 > > If I understand correctly changing the CPUID L3 cache infos in QEMU wil= l change > > the value displayed in the guest /proc/cpuinfo but will not change the = size of > > the l3 cache used by the hardware. So I am chasing a cosmetic bug. > > If it right ? > >=20 > Right. >=20 Well, actually not entirely. An application can query cache sizes and adjust its algorithms accordingly in which case performance can be suboptimal if information in a guest is not accurate. -- Gleb.