Re: Re: ktap inclusion in drivers/staging/?

[Ingo Molnar]

* Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx> wrote:

> (2013/10/26 17:59), Ingo Molnar wrote:
> > 
> > * Jovi Zhangwei <jovi.zhangwei@xxxxxxxxx> wrote:
> > 
> >> Thanks. An addition question I want to discuss in here is the ktap 
> >> code structure layout in first patch series, this don't need to 
> >> dig out any ktap design detail, so we can make agreement on this 
> >> point, and ease for me to prepare patch series.
> >>
> >> Do I need to prepare patchset target on staging tree or "real" 
> >> part of kernel? [...]
> > 
> > I'd suggest adding it to the core, i.e. kernel/tracing/ and 
> > kernel/trace/trace_events_filter.c in particular which includes the 
> > current filter script interpreter.
> 
> It means we'll need to put Lua compiler in the kernel...

How big is a reasonable implementation right now?

> Would you mean the bytecode should be decodable? or loaded with 
> source code in the kernel?

Loaded with the source code into the kernel - like OpenGL shader 
source code is loaded. (except that there's no bin-only exception.)

These are small scripts most of whom are (much) smaller than a 
single page.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/