9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Robert Raschke" <rtrlists@googlemail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: [9fans] P9P libthread on Debian ARM vs. makecontext et al.
Date: Tue,  8 Jul 2008 14:01:27 +0100	[thread overview]
Message-ID: <6a3ae47e0807080601m30b6da97w782bde83f91055cf@mail.gmail.com> (raw)

Hi,

I recently got myself a lovely Nokia N810 internet tablet. That runs
Debian ARM and I thought I'd have a stab at compiling P9P for it.
Unfortunately, the makecontext/swapcontext calls are not supported on
that platform by Debian.

I noticed that libthread/Linux.c has implementations of those two
functions for ARM. So I thought I try compiling libthread without
pthread support. This time, it's the mcontext_t (aka sigcontext)
struct that is causing an issue. The Debian ARM sigcontext struct
looks like this:

struct sigcontext {
    unsigned long trap_no;
    unsigned long error_code;
    unsigned long oldmask;
    unsigned long arm_r0;
...
    unsigned long arm_r10;
    unsigned long arm_fp;
    unsigned long arm_ip;
    unsigned long arm_sp;
    unsigned long arm_lr;
    unsigned long arm_pc;
    unsigned long arm_cpsr;
    unsigned long fault_address;
};

The code in Linux.c that implements makecontext() for ARM expects this
struct to contain a gregs array. I'm guessing that gregs is the same
as the enumerated arm_* ones above. So, would I be correct in assuming
that gregs[13] is arm_sp and gregs[14] is arm_lr?

Thanks,
Robby



             reply	other threads:[~2008-07-08 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 13:01 Robert Raschke [this message]
2008-07-08 14:05 ` Michael Teichgräber
2008-07-08 15:59   ` Robert Raschke

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=6a3ae47e0807080601m30b6da97w782bde83f91055cf@mail.gmail.com \
    --to=rtrlists@googlemail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).