Joerg Roedel <joro@xxxxxxxxxx> writes: > On Mon, Mar 22, 2010 at 11:59:27AM +0100, Ingo Molnar wrote: > > Best would be if you demonstrated any problems of the perf symbol lookup code > > you are aware of on the host side, as it has that exact design you are > > criticising here. We are eager to fix any bugs in it. > > > > If you claim that it's buggy then that should very much be demonstratable - no > > need to go into theoretical arguments about it. > > I am not claiming anything. I just try to imagine how your proposal > will look like in practice and forgot that symbol resolution is done at > a later point. > But even with defered symbol resolution we need more information from > the guest than just the rip falling out of KVM. The guest needs to tell > us about the process where the event happened (information that the host > has about itself without any hassle) and which executable-files it was > loaded from. Slightly tangential, but there is another case that has some of the same problems: profiling other language runtimes than C and C++, say Python. At the moment profilers will generally tell you what is going on inside the python runtime, but not what the python program itself is doing. To fix that problem, it seems like we need some way to have python export what is going on. Maybe the same mechanism could be used to both access what is going on in qemu and python. Soren -- 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
