linux-mips
[Top] [All Lists]

Re: debian's mips userland on mips64

To: Andrew Clausen <clausen@melbourne.sgi.com>
Subject: Re: debian's mips userland on mips64
From: Christoph Hellwig <hch@sgi.com>
Date: Wed, 22 Jan 2003 12:45:40 -0500
Cc: linux-mips@linux-mips.org, gnb@melbourne.sgi.com
In-reply-to: <20030122073006.GF6262@pureza.melbourne.sgi.com>; from clausen@melbourne.sgi.com on Wed, Jan 22, 2003 at 06:30:06PM +1100
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030122073006.GF6262@pureza.melbourne.sgi.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5.1i
On Wed, Jan 22, 2003 at 06:30:06PM +1100, Andrew Clausen wrote:
> Hi all,
> 
> I'm playing with Debian on an Origin 200 (aka ip27 - 64-bit mips).
> The current setup in the mips64-linux world is 64bit kernel +
> 32bit userland.  So, a mips64-linux kernel can be mostly run a
> mips32-linux userland out of the box.
> 
> Unfortunately, this doesn't apply to strace, as this play with
> the 64bit kernel's stack (eg: struct pt_regs), which is different in
> mips32 and mips64.
> 
> So, I guess the solution is to hack (it's ugly as hell already...)
> strace to detect and understand the 64 bit stack from a 32 bit
> userland?

I don't think so.  You should rather implement a sys32_ptrace and
reference it in the 32bit syscall vector.  Look at the version in
arch/ia64/ia32/sys_ia32.c for an example.


<Prev in Thread] Current Thread [Next in Thread>