From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
"Gleb Natapov" <gleb@redhat.com>,
qemu-devel@nongnu.org, "Igor Mammedov" <imammedo@redhat.com>,
pbonzini@redhat.com, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] KVM guest cpu L3 cache and cpufreq
Date: Tue, 27 Aug 2013 15:18:16 +0200 [thread overview]
Message-ID: <20130827131816.GA5436@irqsave.net> (raw)
In-Reply-To: <20130826204729.GW2631@otherpad.lan.raisama.net>
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 size 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 edx register ?
>
> 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 to the
guest ?
>
> > What would be an acceptable user interface to set this ?
>
> Things I can remember from the top of my head:
>
> * It would be interesting to redo this patch, before doing anything else:
> https://github.com/ehabkost/qemu-hacks/commit/10b675fa1269a65a553586545fdbcd95ace79d65
> * 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 the
leaves or does the machine type rule apply here ?
Best regards
Benoît
next prev parent reply other threads:[~2013-08-27 13:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 18:17 [Qemu-devel] KVM guest cpu L3 cache and cpufreq Benoît Canet
2013-08-26 12:40 ` Gleb Natapov
2013-08-26 12:49 ` Benoît Canet
2013-08-26 14:33 ` Gleb Natapov
2013-08-26 16:45 ` Benoît Canet
2013-08-26 20:47 ` Eduardo Habkost
2013-08-27 13:18 ` Benoît Canet [this message]
2013-08-27 13:17 ` Gleb Natapov
2013-08-27 13:20 ` Gleb Natapov
2013-08-27 13:35 ` Benoît Canet
2013-08-27 13:39 ` Gleb Natapov
2013-08-27 13:37 ` Eduardo Habkost
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=20130827131816.GA5436@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).