From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47282) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEJ8F-0002ON-Dw for qemu-devel@nongnu.org; Tue, 27 Aug 2013 09:16:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VEJ8A-0003NC-MR for qemu-devel@nongnu.org; Tue, 27 Aug 2013 09:16:27 -0400 Received: from nodalink.pck.nerim.net ([62.212.105.220]:33196 helo=paradis.irqsave.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEJ8A-0003Mr-Ct for qemu-devel@nongnu.org; Tue, 27 Aug 2013 09:16:22 -0400 Date: Tue, 27 Aug 2013 15:18:16 +0200 From: =?iso-8859-1?Q?Beno=EEt?= Canet Message-ID: <20130827131816.GA5436@irqsave.net> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20130826204729.GW2631@otherpad.lan.raisama.net> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] KVM guest cpu L3 cache and cpufreq List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: =?iso-8859-1?Q?Beno=EEt?= Canet , Gleb Natapov , qemu-devel@nongnu.org, Igor Mammedov , pbonzini@redhat.com, Andreas =?iso-8859-1?Q?F=E4rber?= Hello Eduardo, I read a bit about caches on wikipedia. If I understand correctly changing the CPUID L3 cache infos in QEMU will = change the value displayed in the guest /proc/cpuinfo but will not change the si= ze of the l3 cache used by the hardware. So I am chasing a cosmetic bug. If it right ? > > Do you have some recommandations regarding the other fields of the ed= x register ? >=20 > Probably it will be a good idea to let each CPU model have their own > defaults for the cache information. Do you mean querying the host CPUID registers and forwarding the values t= o the guest ? >=20 > > What would be an acceptable user interface to set this ? >=20 > Things I can remember from the top of my head: >=20 > * It would be interesting to redo this patch, before doing anything el= se: > https://github.com/ehabkost/qemu-hacks/commit/10b675fa1269a65a553586= 545fdbcd95ace79d65 > * We need to keep compatibility on existing machine-types (not change > the cache size); > * If some information is reported on multiple CPUID leaves, we need to > keep them consistent with each other (see the FIXME comments on the > URL above); I could write a patch to fix broken CPUID leaves. But how would it work regarding compatibility ? Is it right to just fix t= he leaves or does the machine type rule apply here ? Best regards Beno=EEt