aboutsummaryrefslogtreecommitdiffstats
path: root/tools/xenmon/README
diff options
context:
space:
mode:
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>2006-04-14 14:21:12 +0100
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>2006-04-14 14:21:12 +0100
commite4287d87ae819e65b7bd4a074264c184959475d9 (patch)
treea646bceb0d034c37404a1903911edb55ffa08eb8 /tools/xenmon/README
parent2256643d06799d4ff0b1f7c5e542cd5af6f7670e (diff)
downloadxen-e4287d87ae819e65b7bd4a074264c184959475d9.tar.gz
xen-e4287d87ae819e65b7bd4a074264c184959475d9.tar.bz2
xen-e4287d87ae819e65b7bd4a074264c184959475d9.zip
This is a patch for XenMon which only applies to the userspace tools.
The primary purpose of this patch is to add support for non-polling access to the xen trace buffers. The hypervisor changes have already been accepted. Also included are a few bug fixes and some minor new features: 1. If xenmon is run without first allocating trace buffers (via 'setsize') and enabling them (via 'tbctl'), then this is done automatically using sensible defaults. 2. There was a bug that caused the first second's worth of data output from xenmon to be erroneous; This has been fixed. 3. There was a bug that caused xenmon to sometimes not display data for newly created domains; This has also been fixed. 4. The xenmon display has a 'heartbeat' which flickers once per second. This is to show that xenmon is still alive, even though the display isn't changing at all, a situation that can happen sometimes when there is nothing at all happening on a particular cpu. 5. Added cpu utilization display to the top of the xenmon window. 6. Added a bunch of options in xenmon to control exactly which metrics are displayed, so the screen doesn't get cluttered with stuff you're not interested in. The new options are: --allocated --noallocated --blocked --noblocked --waited --nowaited --excount --noexcount --iocount --noiocount 7. Added an option ("--cpu=N") to xenmon to specify which physical cpu you'd like data displayed for. 8. Updated the README with information about default trace buffer size, etc. Signed-off-by: Rob Gardner <rob.gardner@hp.com>
Diffstat (limited to 'tools/xenmon/README')
-rw-r--r--tools/xenmon/README10
1 files changed, 10 insertions, 0 deletions
diff --git a/tools/xenmon/README b/tools/xenmon/README
index c717daef88..3393f5b8ce 100644
--- a/tools/xenmon/README
+++ b/tools/xenmon/README
@@ -84,6 +84,16 @@ Usage Notes and issues
events cause a trace record to be emitted.
- To exit xenmon, type 'q'
- To cycle the display to other physical cpu's, type 'c'
+ - The first time xenmon is run, it attempts to allocate xen trace buffers
+ using a default size. If you wish to use a non-default value for the
+ trace buffer size, run the 'setsize' program (located in tools/xentrace)
+ and specify the number of memory pages as a parameter. The default is 20.
+ - Not well tested with domains using more than 1 virtual cpu
+ - If you create a lot of domains, or repeatedly kill a domain and restart it,
+ and the domain id's get to be bigger than NDOMAINS, then xenmon behaves badly.
+ This is a bug that is due to xenbaked's treatment of domain id's vs. domain
+ indices in a data array. Will be fixed in a future release; Workaround:
+ Increase NDOMAINS in xenbaked and rebuild.
Future Work
-----------