* Avi Kivity<avi@xxxxxxxxxx> wrote:
On 03/16/2010 01:25 PM, Ingo Molnar wrote:How do i get a list of all 'guest instance PIDs',
We know its pid.I haven't followed vmchannel closely, but I think it is. vmchannel isHm, that sounds rather messy if we want to use it to basically expose kernel
terminated in qemu on the host side, not in the host kernel. So perf would
need to connect to qemu.
functionality in a guest/host unified way. Is the qemu process discoverable in
some secure way?
and what is the way to talk
to Qemu?
I mean, i can trust a kernel service and i can trust /proc/kallsyms.Can we trust it?No choice, it contains the guest address space.
Can perf trust a random process claiming to be Qemu? What's the trust
mechanism here?
So Qemu has never run into such problems before?Is there some proper tooling available to do it, or do we have to push itlibvirt manages qemu processes, but I don't think this should go through
through 2-3 packages to get such a useful feature done?
libvirt. qemu can do this directly by opening a unix domain socket in a
well-known place.
( Sounds weird - i think Qemu configuration itself should be done via a
unix domain socket driven configuration protocol as well. )
Certainly not, but this is a technical problem in the kernel's domain, so it's( That is the general thought process how many cross-discipline usefulYou can't solve everything in the kernel, even with a well populated tools/.
desktop/server features hit the bit bucket before having had any chance of
being vetted by users, and why Linux sucks so much when it comes to feature
integration and application usability. )
a fair (and natural) expectation to be able to solve this within the kernel
project.