| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Xenoprof and the hypervisor
The sample is delivered to the VCPU (and associated domain) that is
currently running on the CPU when the sample is taken,
as computed by the Xen macro "current". That means that samples
taken when a harware interrupt is running are associated
with the VCPU/domain that was interrupted by the HW interrupt.
Renato
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>> David Carr
>> Sent: Tuesday, May 23, 2006 2:12 PM
>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: [Xen-devel] Xenoprof and the hypervisor
>>
>> Thanks in part to Jose's help I've gotten oprofile working
>> on multiple domains with unstable. After reading the
>> original Xenoprof paper, I have a question about how
>> hypervisor samples are handled. If my understanding is
>> correct, all samples pass through the hypervisor where they
>> are then dispatched to the profiler in the corresponding
>> domain. This makes sense in the case where code running in
>> a given domain makes a hypercall.
>> However, what happens when a hardware interrupt triggers
>> code execution in the hypervisor? Where do such samples end
>> up getting dispatched to and recorded?
>>
>> Thanks,
>> David Carr
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home