oerg Roedel wrote: > On Tue, Mar 16, 2010 at 12:25:00PM +0100, Ingo Molnar wrote: >> Hm, that sounds rather messy if we want to use it to basically expose kernel >> functionality in a guest/host unified way. Is the qemu process discoverable in >> some secure way? Can we trust it? Is there some proper tooling available to do >> it, or do we have to push it through 2-3 packages to get such a useful feature >> done? > > Since we want to implement a pmu usable for the guest anyway why we > don't just use a guests perf to get all information we want? If we get a > pmu-nmi from the guest we just re-inject it to the guest and perf in the > guest gives us all information we wand including kernel and userspace > symbols, stack traces, and so on. I guess this aims to get information from old environments running on kvm for life extension :) > In the previous thread we discussed about a direct trace channel between > guest and host kernel (which can be used for ftrace events for example). > This channel could be used to transport this information to the host > kernel. Interesting! I know the people who are trying to do that with systemtap. See, http://vesper.sourceforge.net/ > > The only additional feature needed is a way for the host to start a perf > instance in the guest. # ssh localguest perf record --host-chanel ... ? B-) Thank you, > > Opinions? > > > Joerg > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Masami Hiramatsu e-mail: mhiramat@xxxxxxxxxx -- 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
