> > But we then need to predefine many probes for decoding to work in the form > > of > > func:offset, and then play catch-up with all the kernel changes. > > Or I miss something important here? > > No you don't. > > If we want to disturb the system in the least way possible, we need to > tag along the copying from userspace of those pointers, so that we get > them fresh and just stash it in our ring buffer and get out of the way > quickly. I just thought maybe you have some grand plan in mind about automagically adding probes so argument tracing works transparently. I like the approach though.
> Almost a year ago, and it still works, now lets see the cset you mention... > > [acme@zoo linux]$ git describe c4ad8f98bef77c7356aa6a9ad9188a6acc6b849d > v3.14-rc1-14-gc4ad8f98bef7 > [acme@zoo linux]$ > [root@zoo ~]# uname -r > 3.15.0-rc8+ > > Humm, what is the problem? I thought that result->name was actually set on 65th line of getname_flags, so the above commit would move it to 66th. But it's not the case, sorry for confusion. > [1] And I feel like all of tools/perf/ is just that, reference > implementations, but hopefully > done in a such a way that may well be useful as-is :-) I'd like perf to be a goto tool for all kind of performance analysis, not just a reference implementation. I believe nobody looks at this reference, and we end up with tools like https://github.com/draios/sysdig which do their own events, ring buffer, etc. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/