linux-kernel - Re: Re: ktap inclusion in drivers/staging/?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131028121958.GA8641@gmail.com>
Date:	Mon, 28 Oct 2013 13:19:58 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Jovi Zhangwei <jovi.zhangwei@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"zhangwei(Jovi)" <jovi.zhangwei@...wei.com>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Tom Zanussi <tom.zanussi@...ux.intel.com>,
	Namhyung Kim <namhyung@...nel.org>,
	David Ahern <dsahern@...il.com>, Jiri Olsa <jolsa@...hat.com>
Subject: Re: Re: ktap inclusion in drivers/staging/?


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

> (2013/10/26 17:59), Ingo Molnar wrote:
> > 
> > * Jovi Zhangwei <jovi.zhangwei@...il.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/