LTTng-core (basic tracing infrastructure) 0.5.108
In-Reply-To: <[email protected]>
Quoted 9 lines · Alan Cox
Quoted 6 lines
$ grep KPROBES arch/*/Kconf* arch/i386/Kconfig:config KPROBES arch/ia64/Kconfig:config KPROBES arch/powerpc/Kconfig:config KPROBES arch/sparc64/Kconfig:config KPROBES arch/x86_64/Kconfig:config KPROBESSend patches. The fact nobody has them implemented on your platform isn't a reason to implement something else, quite the reverse in fact.
Yes, but the point is: until that's done you can't claim kprobes is a valid tracing tool for everyone.
And things like net/ipv4/tcp_probe.c shouldn't be generally implemented until every arch is supported.
Signature · 1 line
Chuck
Ar Gwe, 2006-09-15 am 13:14 -0400, ysgrifennodd Chuck Ebbert:
Quoted 8 lines
In-Reply-To: <[email protected]>
Quoted 7 lines
Quoted 6 lines
$ grep KPROBES arch/*/Kconf* arch/i386/Kconfig:config KPROBES arch/ia64/Kconfig:config KPROBES arch/powerpc/Kconfig:config KPROBES arch/sparc64/Kconfig:config KPROBES arch/x86_64/Kconfig:config KPROBES
Quoted 5 lines
Quoted 2 lines
Send patches. The fact nobody has them implemented on your platform isn't a reason to implement something else, quite the reverse in fact.
Yes, but the point is: until that's done you can't claim kprobes is a valid tracing tool for everyone.
I can however claim that kprobes is what they should be implementing not adding new large patches for another infrastructure whose author has already said for dynamic stuff it is based on the same things.
Quoted 10 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
Quoted 6 lines · Alan Cox
Quoted 6 lines
$ grep KPROBES arch/*/Kconf* arch/i386/Kconfig:config KPROBES arch/ia64/Kconfig:config KPROBES arch/powerpc/Kconfig:config KPROBES arch/sparc64/Kconfig:config KPROBES arch/x86_64/Kconfig:config KPROBES
Quoted 5 lines
Quoted 2 lines
Send patches. The fact nobody has them implemented on your platform isn't a reason to implement something else, quite the reverse in fact.
Yes, but the point is: until that's done you can't claim kprobes is a valid tracing tool for everyone.
The fact that the remaining architectures haven't bothered implementing kprobe supposed should not be used as an argument for pushing something inferior out of laziness.
It's the same with syscalls, the kernel infrastructure is there, but if you don't bother updating the syscall tables and wrap it in with glibc, then the call isn't available on your architecture.
The core kprobe infrastructure is available to all architectures, it's up to the developers of the remaining architectures to implement the remaining bits.
Jes