>> ... which is a binary only, proprietary application.
>
>The IA32 emulation part of it is actually shipped in source.
>Somehow they manage to link a binary only object to it though.
There are two parts to the ia32 emulation ... the part that handles
all the Linux syscall emulation is open (LGPL I think). The part
that handles translation of x86 instructions into ia64 instructions
is the binary only part ... a shared library that gets attached by
the Linux layer ... this same binary blob is used on all operating
systems.
>> Either way, either the emulation is in the kernel or it's not. If it's
>> there (like it is now) it deserves maintenance. If it's not, it should
>> be removed from the tree, since the only thing it's otherwise good for
>> is potential security holes.
>
>I suppose it's still useful for all current IA64 users (Montecito
>is not shipping yet and older CPUs support x86 in hardware) who don't like
>binary only software.
I was planning on asking who still depends on the emulation code
a while after Montecito is shipping. Until then I'll try to do
what makes sense in keeping the ia32 emulation system call table
up to date.
The perfmon syscalls would be an example of something that should
*NOT* go into the ia32 emulation syscall table. It makes no sense
whatever to put them there. I don't believe that the h/w emulation
provides any performance counter emulation, and even if it did a
user who cared about the performance of their application would do
far better to re-compile it as native ia64 than to mess around
trying to optimize their x86 binary.
-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]