On Tue, Apr 08, 2014 at 04:40:36PM +0900, Masami Hiramatsu wrote: > (2014/04/07 22:55), Peter Zijlstra wrote: > > On Wed, Apr 02, 2014 at 09:42:03AM +0200, Ingo Molnar wrote: > >> I'd suggest using C syntax instead initially, because that's what the > >> kernel is using. > >> > >> The overwhelming majority of people probing the kernel are > >> programmers, so there's no point in inventing new syntax, we should > >> reuse existing syntax! > > > > Yes please, keep it C, I forever forget all other syntaxes. While I have > > in the past known other languages, I never use them frequently enough to > > remember them. And there's nothing more frustrating than having to fight > > a tool/language when you just want to get work done. > > Why wouldn't you write a kernel module in C directly? :) > It seems that all what you need is not a tracing language nor a bytecode > engine, but an well organized tracing APIs(library?) for writing a kernel > module for tracing...
Most my kernels are CONFIG_MODULE=n :-) Also, I never can remember how to do modules. That said; what I currently do it hack the kernel with debug bits and pieces and run that, which is effectively the same. Its just that its impossible to save/share these hacks in any sane fashion. -- 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/
