|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] [PATCH] add oprofile Kconfig
This is a trivial patch to add kernel config support for oprofile. I
have been using oprofile for the last few days (timer int based) and it
seems to work "OK". IMO, oprofile could stand a lot of virtualization
awareness, and I would like to discuss what everyone would like to see.
I would like oprofile to have the ability to profile the entire system,
including xen and all running domains. I would think running oprofile
daemon in dom0 would be adequate, as long as we could (a) modify
oprofile driver to tell xen what kind of events we need (b) have xen
forward data for those events to dom0 (c) add info in that data that
tells oprofile what domain or if xen was running (d) modify oprofile
reporters to be aware of the new data and have reference to bins in
other running domains.
I suppose oprofile could still be run in a domU, but probably just timer
int based profiling. If one would want to use perf counters in just the
context of a single domU, I guess we would have to save/restore that
data on the cpus as we switch from/to that domU?
-Andrew Theurer
diff -Naurp xen-unstable-orig/linux-2.6.10-xen-sparse/arch/xen/Kconfig.drivers
xen-unstable/linux-2.6.10-xen-sparse/arch/xen/Kconfig.drivers
--- xen-unstable-orig/linux-2.6.10-xen-sparse/arch/xen/Kconfig.drivers
2005-02-24 22:12:10.000000000 -0600
+++ xen-unstable/linux-2.6.10-xen-sparse/arch/xen/Kconfig.drivers
2005-02-25 14:55:49.410321096 -0600
@@ -52,4 +52,6 @@ config UNIX98_PTYS
default y
endif
+source "arch/i386/oprofile/Kconfig"
+
endmenu
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-devel] [PATCH] add oprofile Kconfig,
Andrew Theurer <=
|
|
|
|
|