Re: [Qemu-devel] [PATCH 2/4] Octeon cpu definitions in target-mips and Octeon specific changes in set_thread_area syscall

[Richard Henderson]

On 08/17/2011 12:00 AM, Khansa Butt wrote:
> with out above fix Octeon user mode binary can not be correctly run
> on QEMU. This was the behavior on actual hardware which we noticed
> when we were debugging the user mode binary on Octeon board. (there
> are instructions in user mode ELF of Octeon which read k0 and k1
> values)

So you're running a modified compiler, libc, and kernel as well?

Because if I look in Linux 3.1-rc2, arch/mips/kernel/syscall.c,
set_thread_area and arch/mips/kernel/process.c, copy_thread,
I see no evidence that any mips variant uses k0 or k1 for TLS.

You should keep this change alongside whatever modified runtime
you are using.  It does not belong upstream in QEMU until your
changes are accepted upstream in linux as well.


r~