On Wed, 21 Jul 2010 14:17:23 +0900, Bruno Randolf b...@einfach.org wrote:
but that's for all tracepoints all over the kernel... i think it's natural
that this takes some CPU time. note that on these boards even the 22Mbps are
limited by the CPU processing power.
The key word here is some.
On Wed, 2010-07-21 at 14:17 +0900, Bruno Randolf wrote:
but that's for all tracepoints all over the kernel...
Well you definitely don't want to enable like function graph tracing,
that's expected to be more expensive unless you also have the callsite
patching version of it. But _just_ enabling
On Thu July 22 2010 13:55:36 Jonathan Guerin wrote:
Hi all,
I'm not sure if I'm just misunderstanding something, or if they
documentation is older than what's happening in practice. I'm trying
to enable ath5k debug mode so that I can have a poke around in debufs.
Unfortunately, enabling
Hi all,
I'm not sure if I'm just misunderstanding something, or if they
documentation is older than what's happening in practice. I'm trying
to enable ath5k debug mode so that I can have a poke around in debufs.
Unfortunately, enabling debug in the compat-wireless distro doesn't
seem to output
