Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@sgi.com>
To: Andrew Clausen <clausen@melbourne.sgi.com>
Cc: linux-mips@linux-mips.org, gnb@melbourne.sgi.com
Subject: Re: debian's mips userland on mips64
Date: Wed, 22 Jan 2003 12:45:40 -0500	[thread overview]
Message-ID: <20030122124540.A31505@sgi.com> (raw)
In-Reply-To: <20030122073006.GF6262@pureza.melbourne.sgi.com>; from clausen@melbourne.sgi.com on Wed, Jan 22, 2003 at 06:30:06PM +1100

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.

  reply	other threads:[~2003-01-22 10:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22  7:30 debian's mips userland on mips64 Andrew Clausen
2003-01-22 17:45 ` Christoph Hellwig [this message]
2003-01-22 12:45   ` Ralf Baechle
2003-01-22 20:09     ` Christoph Hellwig
2003-01-23  3:05       ` Greg Banks
2003-01-23  5:04         ` Ralf Baechle
2003-01-22 21:47   ` Greg Lindahl
2003-01-28  7:00     ` Ralf Baechle
     [not found] ` <002001c2cba5$ab641320$4437e183@fermi.win.fnal.gov>
2003-02-03 22:56   ` Andrew Clausen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030122124540.A31505@sgi.com \
    --to=hch@sgi.com \
    --cc=clausen@melbourne.sgi.com \
    --cc=gnb@melbourne.sgi.com \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox