From: "Yuvraj Agarwal" <yuvraj@cs.ucsd.edu>
To: xen-devel@lists.xensource.com
Subject: Measuring the amount of memory read/written (basically touched) by a domU
Date: Mon, 3 May 2010 12:21:54 -0700 (PDT) [thread overview]
Message-ID: <040601caeaf5$e5951400$b0bf3c00$@ucsd.edu> (raw)
In-Reply-To: <d72ec2ffeb67195d55e9.1272912831@kremvax.cs.ubc.ca>
Hi,
We want to measure the amount of memory that a domU touches while its
running, and if possible even get a breakdown between memory read/written.
We want to basically do these measurements for some windows domUs (XP,
vista, 7) and perhaps even linux domU's on top of XEN... Does anyone know
how do I can get this information easily? Has anyone done something like
this already?
My test system is using XEN 4.0 + 2.6.32 pvops kernel -- (Ubuntu 9.10)
Thanks!
Yuvraj
next prev parent reply other threads:[~2010-05-03 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 18:53 [PATCH 0 of 7] Remus: pvops dom0 support Brendan Cully
2010-05-03 18:53 ` [PATCH 1 of 7] Remus: python netlink fixes Brendan Cully
2010-05-03 18:53 ` [PATCH 2 of 7] Remus: remove obsolete code Brendan Cully
2010-05-03 18:53 ` [PATCH 3 of 7] Remus: move device handling into its own module Brendan Cully
2010-05-03 18:53 ` [PATCH 4 of 7] Remus: fix VM stringification Brendan Cully
2010-05-03 19:21 ` Yuvraj Agarwal [this message]
2010-05-03 19:32 ` Measuring the amount of memory read/written (basically touched) by a domU Keir Fraser
2010-05-03 18:53 ` [PATCH 5 of 7] Remus: include device name in vif objects Brendan Cully
2010-05-03 18:53 ` [PATCH 6 of 7] Remus: add file locking and modprobe utility functions Brendan Cully
2010-05-03 18:53 ` [PATCH 7 of 7] Remus: use IFB for net buffer on newer kernels Brendan Cully
2010-05-03 20:05 ` [PATCH 0 of 7] Remus: pvops dom0 support Gilberto Nunes
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='040601caeaf5$e5951400$b0bf3c00$@ucsd.edu' \
--to=yuvraj@cs.ucsd.edu \
--cc=xen-devel@lists.xensource.com \
/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).