[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100907141319.C90D.A69D9226@jp.fujitsu.com>
Date: Tue, 7 Sep 2010 19:57:22 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Pekka Enberg <penberg@...nel.org>
Cc: kosaki.motohiro@...fujitsu.com, Ingo Molnar <mingo@...e.hu>,
Avi Kivity <avi@...hat.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Tom Zanussi <tzanussi@...il.com>,
Frédéric Weisbecker <fweisbec@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-perf-users@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: disabling group leader perf_event
> As for the intermediate form, you might want to take a look at Dalvik:
>
> http://www.netmite.com/android/mydroid/dalvik/docs/dalvik-bytecode.html
>
> and probably ParrotVM bytecode too. The thing to avoid is stack-based
> instructions like in Java bytecode because although it's easy to write
> interpreters for them, it makes JIT'ing harder (which needs to convert
> stack-based representation to register-based) and probably doesn't
> lend itself well to stack-constrained kernel code.
(offtopic)
Afaik, NetBSD plan to include lua interpreter in kernel. it is optimized embedded environment.
(more offtopic)
in kernel interpreter is needed some concern. 1) restricted stack size (typical userland VM
often use >100K stack size) 2) restrected memory allocation, especially high order allocation
often fail. 3) GC often makes unacceptable large lag especially on UP kernel. etc etc
So, We can't apply rich interpreter (e.g. Dalvik, Parrrot) so easily. I think. personally I prefer
minimum component.
Thanks.
--
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/
Powered by blists - more mailing lists