All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jd <jd_jedi@convirture.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Intel Haswell : Cache monitoring technology and libvirt
Date: Thu, 25 Sep 2014 12:00:16 -0700	[thread overview]
Message-ID: <54246640.1080902@convirture.com> (raw)

Hi
We are looking to get processor level cache metrics for each running VM.
Does QEMU/KVM (or libvirt) set RMID for tagging processor cache metrics 
? How do I find RMID for a particular VM ?
(Once RMID is known, I am assuming we will be able to query the 
processor via MSRs to get values)
Any help / pointers will be appreciated.

Thanks
/Jd

Some more context :

https://01.org/blogs/skjain/2014/four-new-virtualization-technologies-latest-intel%C2%AE-xeon-are-you-ready-innovate

*Cache Monitoring Technology (CMT)* - allows flexible real time 
monitoring of the last level cache (LLC) occupancy on per core, per 
thread, per application or per VM basis. Read the raw value from the 
IA32_QM_CTR register, multiply by a factor given in the CPUID field 
CPUID.0xF.1:EBX to convert to bytes, and voila! This monitoring can be 
quite useful in detecting the cache hungry “noisy neighbors,” 
characterizing the quiet threads, profiling the workloads in 
multi-tenancy environments, advancing cache-aware scheduling and/or all 
of the above. Based on the CMT readings, schedulers can take subsequent 
intelligent actions to move and balance the loads to meet any service 
level agreement (SLA) in a policy driven manner. Intel® 64 and IA-32 
Architectures Software Developer’s Manual (SDM) volume-3 chapter-17.14 
provides the CMT programming details. CMT reference code is also 
available for evaluation under BSD license. For commercial use, please 
use the CMT cgroup and perf monitoring code being upstreamed for Linux, 
and both KVM and Xen.

                 reply	other threads:[~2014-09-25 19:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=54246640.1080902@convirture.com \
    --to=jd_jedi@convirture.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.