From: "Benoît Canet" <benoit.canet@irqsave.net>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, gleb@redhat.com
Subject: [Qemu-devel] KVM guest cpu L3 cache and cpufreq
Date: Tue, 13 Aug 2013 20:17:13 +0200 [thread overview]
Message-ID: <20130813181713.GA5204@irqsave.net> (raw)
Hi,
I noticed that the l3 cache size of a guest /proc/cpuinfo is not the same as
the l3 cache size of the host.
I did not found any references to this in the qemu and KVM code.
Is the size of the guest L3 cache fixed in hardware ?
Can a patch be written to set it ?
Similarly I noticed that the frequency in the guest was not reflecting the
frequency scaling of the host.
Could anything be done for this ?
Best regards
Benoît
next reply other threads:[~2013-08-13 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 18:17 Benoît Canet [this message]
2013-08-26 12:40 ` [Qemu-devel] KVM guest cpu L3 cache and cpufreq 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
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=20130813181713.GA5204@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=gleb@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).