[opensuse-kernel] tracer in 2.6.32...
Hey all, any particular reason why approximately all tracers in the kernel are not compiled as modules by default in 2.6.32rc? In particular, I'm interested in the sysprof tracer, because I use sysprof every now and then. I checked the config, and all CONFIG_*_TRACER are not set. I don't see the reasoning behind that ATM, as the according tracer can only be loaded and activated by root. Thanks Matthias -- Matthias Hopf <mhopf@suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
At Wed, 2 Dec 2009 18:51:57 +0100, Matthias Hopf wrote:
Hey all,
any particular reason why approximately all tracers in the kernel are not compiled as modules by default in 2.6.32rc? In particular, I'm interested in the sysprof tracer, because I use sysprof every now and then. I checked the config, and all CONFIG_*_TRACER are not set.
I don't see the reasoning behind that ATM, as the according tracer can only be loaded and activated by root.
I also don't know the reason, but doesn't perf work enough for you? Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Dec 02, 09 19:12:03 +0100, Takashi Iwai wrote:
any particular reason why approximately all tracers in the kernel are not compiled as modules by default in 2.6.32rc? In particular, I'm interested in the sysprof tracer, because I use sysprof every now and then. I checked the config, and all CONFIG_*_TRACER are not set.
I don't see the reasoning behind that ATM, as the according tracer can only be loaded and activated by root.
I also don't know the reason, but doesn't perf work enough for you?
Not even close. You need to recompile for perf, it only profiles a single application, output is unreadable. oprofile also doesn't work. While in theory it should be better, I couldn't get it working correctly (stack traces > 2 entries), there was no (zero) support for getting it working, and output is unreadable. sysprof just flies, is trivial to use, has a very reasonable GUI tool, and is good enough. Matthias -- Matthias Hopf <mhopf@suse.de>, SuSE R&D, Zimmer 2.2.6, Tel. 74053-715 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Thu, Dec 03, 2009 at 03:45:12PM +0100, Matthias Hopf wrote:
On Dec 02, 09 19:12:03 +0100, Takashi Iwai wrote:
any particular reason why approximately all tracers in the kernel are not compiled as modules by default in 2.6.32rc? In particular, I'm interested in the sysprof tracer, because I use sysprof every now and then. I checked the config, and all CONFIG_*_TRACER are not set.
I don't see the reasoning behind that ATM, as the according tracer can only be loaded and activated by root.
I also don't know the reason, but doesn't perf work enough for you?
Not even close. You need to recompile for perf, it only profiles a single application, output is unreadable.
Are we talking about the same /usr/bin/perf packaged in 11.2? I can't see why (for the -trace flavor) CONFIG_*_TRACER should not be enabled. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (3)
-
Matthias Hopf -
Takashi Iwai -
Tony Jones