| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] [PATCH] Xenoprof patches for xen-unstable
>> -----Original Message-----
>> From: Nivedita Singhvi [mailto:niv@xxxxxxxxxx]
>> Sent: Wednesday, May 25, 2005 12:23 PM
>> To: Santos, Jose Renato G
>> Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-devel] [PATCH] Xenoprof patches for xen-unstable
>>
>>
>> Santos, Jose Renato G wrote:
>>
>> > hi,
>> >
>> > I have attached patches for enabling system wide profiling
>> > using oprofile for xen unstable.
>> > The patches were generated against change-set 1.1507 (May 22).
>> > The 4 attached files are
>>
>> Jose, thanks very much for this! I really needed it...
>>
You are welcome. Please keep me posted on how you are
using it and any insights you may get using xenoprof
>> > 1) xenoprof.txt:
>> > - xenoprof overview and user guide
>> > 2) xenoprof-1.1-xen-3.0-devel.patch:
>> > - patch for xen
>> > 3) xenoprof-1.1-linux-2.6.11:
>> > - patch for linux. Note that this needs to be applied
>> > twice, once to linux-2.6.11-xen0 and once to
>> > linux-2.6.11-xenU. (This is different than the last
>> > patch which was created against the linux sparse tree).
>> > 4) xenoprof-1.1-oprofile-0.8.2:
>> > - patch for oprofile version 0.8.2
>> >
>> > Current known limitation/bugs are
>> > - No support for SMP guests yet.
>> > - when using passive domains, most samples are lost.
>>
>> Excuse my ignorance - what exactly is a passive domain?
>>
Sorry for using the term without explanation.
We call passive domains domains that are
profiled but do not have support for collecting PC samples
(i.e they do not have oprofile running).
In this case their samples are sent to the initiator
domain (usually domain 0) which process the samples on
their behalf. In this case the samples
are not decoded to specific binary files/functions
but are assigned to the whole domain (coarse granularity
profiling). We are planning to enable fine granularity
profiling for the kernel code on passive domains in
the future. However, as I mentioned, xenoprof is not working
properly with passive domains yet.
In the normal mode of operation that is functional
at this time, every domain being profiled must be running
an oprofile kernel module to process the PC samples
generated when they are running. Each domain will
have a partial report of the samples that happened
when they were running.
System wide profiling is obtained by combining the
reports of all profiled domains.
I hope this is clearer now.
Renato
>> > I will be working on these issues and post new patches
>> > when I have them available.
>>
>> thanks!
>>
>> Nivedita
>>
>>
>>
>>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home