On 03/22/2010 10:32 PM, Ingo Molnar wrote:
* Anthony Liguori<anthony@xxxxxxxxxxxxx> wrote:
On 03/22/2010 02:22 PM, Ingo Molnar wrote:
Transitive had a product that was using a KVM context to run their
binary translator which allowed them full access to the host
processes virtual address space range. In this case, there is no
kernel and there are no devices.
And your point is that such vcpus should be excluded from profiling just
because they fall outside the Qemu/libvirt umbrella?
You don't instrument it the way you'd instrument an operating system so no,
you don't want it to show up in perf kvm top.
Erm, why not? It's executing a virtualized CPU, so sure it makes sense to
allow the profiling of it!
It may not make sense to have symbol tables for it, for example it isn't
generated from source code but from binary code for another architecture.
Of course, just showing addresses is fine, but you don't need qemu for that.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
