Re: disabling group leader perf_event

[Pavel Machek]

On Sun 2010-09-12 22:32:58, Ingo Molnar wrote:
> * Pavel Machek <pavel@xxxxxx> wrote:
> > On Sun 2010-09-12 20:48:43, Ingo Molnar wrote:

> > > > >  1- Most (least abstract) specific code: a block of bytecode in the form
> > > > >     of a simplified, executable, kernel-checked x86 machine code block -
> > > > >     this is also the fastest form. [yes, this is actually possible.]
> > > > >Well... if we want to be a bit x86-entric.... can we just reuse ACPI
> > > > >interpretter?
> > > > 
> > > > I hope this was a joke, ACPI won the academy awards for ugliness, 
> > > > ..., bad specification, non-generality, and 
> > 
> > As did i386 instruction set :-).
> 
> Are you kidding? The i386 instruction set may be ugly, but it's 
> implemented in hardware, which has obvious upsides.

I was partly joking. But you have to admit that i386 set is ugly and
badly specified.

And yes, it is implemented in hardware on _i386_, which, true, has
some advantages on i386.(And what about x86-64, btw? Would same
bytecode run natively in both 32 and 64 bit mode?)

And... we'd have to maintain "is this bytecode safe" checker for i386,
and normal emulator for all other architectures.

> The ACPI AML code is just plain ugly.

Yep, but we already have interpreter in the kernel... How many
interpreters is too many? Does it really matter that AML is "ugly"?

You propose adding checker of similary ugly bytecode, and then
interpreter of the same bytecode.

So... let's drop the "use i386 instructions as bytecode idea", ok?

And now... is maintaining ugly interpreter and non-ugly interpreter
preferable to maintaining just the ugly interpreter? Maybe, if it has
significant speed advantages. But does it? What bytecode do you
propose?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/