public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chegu Vinod <chegu_vinod@hp.com>
To: kvm@vger.kernel.org
Subject: How to determine the backing host physical memory for a given guest ?
Date: Wed, 9 May 2012 13:05:12 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120509T134759-734@post.gmane.org> (raw)


Hello,

On an 8 socket Westmere host I am attempting to run a single guest and 
characterize the virtualization overhead for a system intensive 
workload (AIM7-high_systime) as the size of the guest scales (10way/64G, 
20way/128G, ... 80way/512G). 

To do some comparisons between the native vs. guest runs. I have 
been using "numactl" to control the cpu node & memory node bindings for 
the qemu instance.  For larger guest sizes I end up binding across multiple 
localities. for e.g. a 40 way guest :

numactl --cpunodebind=0,1,2,3  --membind=0,1,2,3  \
qemu-system-x86_64 -smp 40 -m 262144 \
<....>

I understand that actual mappings from a guest virtual address to host physical 
address could change. 

Is there a way to determine [at a given instant] which host's NUMA node is 
providing the backing physical memory for the active guest's kernel and 
also for the the apps actively running in the guest ? 

Guessing that there is a better way (some tool available?) than just
diff'ng the per node memory usage...from the before and after output of 
"numactl --hardware" on the host.

Thanks
Vinod




             reply	other threads:[~2012-05-09 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 13:05 Chegu Vinod [this message]
2012-05-09 13:46 ` How to determine the backing host physical memory for a given guest ? Avi Kivity
2012-05-10  1:23   ` Chegu Vinod
2012-05-10 15:34   ` Andrew Theurer
2012-05-11  1:22     ` Chegu Vinod
2012-05-12  2:50       ` Chegu Vinod

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=loom.20120509T134759-734@post.gmane.org \
    --to=chegu_vinod@hp.com \
    --cc=kvm@vger.kernel.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