|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [PATCH] add oprofile Kconfig
To: |
"Andrew Theurer" <habanero@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, <Ian.Pratt@xxxxxxxxxxxx> |
Subject: |
RE: [Xen-devel] [PATCH] add oprofile Kconfig |
From: |
"Santos, Jose Renato G (Jose Renato Santos)" <joserenato.santos@xxxxxx> |
Date: |
Tue, 1 Mar 2005 17:09:42 -0800 |
Cc: |
"G John Janakiraman" <john@xxxxxxxxxxxxxxxxxxx>, "Turner, Yoshio" <yoshio_turner@xxxxxx>, "Aravind Menon" <aravind.menon@xxxxxxx>, "Jose Renato Santos" <jsantos@xxxxxxxxxx> |
Delivery-date: |
Wed, 02 Mar 2005 02:26:52 +0000 |
Envelope-to: |
xen+James.Bulpin@xxxxxxxxxxxx |
List-archive: |
<http://sourceforge.net/mailarchive/forum.php?forum=xen-devel> |
List-help: |
<mailto:xen-devel-request@lists.sourceforge.net?subject=help> |
List-id: |
List for Xen developers <xen-devel.lists.sourceforge.net> |
List-post: |
<mailto:xen-devel@lists.sourceforge.net> |
List-subscribe: |
<https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe> |
List-unsubscribe: |
<https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe> |
Sender: |
xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx |
Thread-index: |
AcUbgBVzPc2gaMsURs+A8YVBoRyWsgDMv38A |
Thread-topic: |
[Xen-devel] [PATCH] add oprofile Kconfig |
We have extended Xen and Oprofile to enable system wide profiling in
Xen x86 platforms (tested so far on pentium 4 and pentium III). We are
currently cleaning up the code and plan to release it to the community
in a few weeks. The code enables profiling across all or any subset of
domains and the hypervisor.
We moved the architecture-specific components of oprofile into Xen
hypervisor to collect PC samples and to program the hw performance
counters. In xenolinux, we created a new architecture-specific component
for Xen that sends commands to Xen using a new hypercall. Samples are
buffered in Xen and transferred to domains using shared pages. Domains
are notified of new samples through virtual interrupts. Samples are
interpreted in each domain, since interpretation of program counters has
to be done in the context of the running process (information that is
domain specific). Thus for detailed profiling information each domain
being profiled need to be running an oprofile module to interpret the
samples. However it is possible to have profiling information for
domains that do not have an oprofile module running (passive domains).
In that case the samples for the passive domain are delivered to another
domain for processing. Although detailed information for passive domains
can not be generated in this case, coarse domain level profiling
information is still available. This may be usefull for domains running
an OS that does not support oprofile (i.e. any OS other than linux).
We have not implemented any virtualization of hw performance counters
(i.e. save/restore hw counters on domain context switch) to enable
independent oprofilig of individual domains. Although this would be
usefull it is not at the top of our priority list.
We have started to use this environment to profile some networking
benchmarks in Xen and found it very usefull to give us insight about
system performance issues. As we compile the results we will post them
to list.
- Renato Santos
HP Labs
>> -----Original Message-----
>> From: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
>> [mailto:xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of
>> Andrew Theurer
>> Sent: Friday, February 25, 2005 1:13 PM
>> To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
>> Subject: [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
>>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] [PATCH] add oprofile Kconfig,
Santos, Jose Renato G (Jose Renato Santos) <=
|
|
|
|
|