9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: lucio@proxima.alt.za,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] P9P on Lemote Yeeloong
Date: Wed, 13 May 2009 15:00:02 -0700	[thread overview]
Message-ID: <dd6fe68a0905131500n5d846348p24c6f3bfb95264e7@mail.gmail.com> (raw)
In-Reply-To: <2b93b6bcf93d8d06edb6ac3a173ade68@proxima.alt.za>

I don't know that p9p has ever been built
on a MIPS machine, so you might run into
more problems after this one.

You are almost certainly running Linux 2.6
so you shouldn't need to edit u.h -- it should
be using pthreads already.

You probably need to edit src/libthread/sysofiles.sh
to add a

case mips-Linux-2.6.*)
    echo pthread.o Linux-mips-context.o
    ;;

Then you'll need to write Linux-mips-context.S and mips-context.h
to provide useful versions of getcontext and setcontext
and change threadimpl.h to use them on MIPS (like it does
for __APPLE__ and __OpenBSD__).

I looked around but I don't think I have any such
implementations lying around.  They're not too hard:
just save and restore every register (technically,
just the callee-saves, but I'm too lazy to look up
which ones are which and too paranoid to trust
them not to change).

Russ


  parent reply	other threads:[~2009-05-13 22:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 19:57 lucio
2009-05-13 20:28 ` Bakul Shah
2009-05-14  3:17   ` lucio
2009-05-13 21:24 ` Latchesar Ionkov
2009-05-14  3:38   ` lucio
2009-05-13 22:00 ` Russ Cox [this message]
2009-05-14  3:34   ` lucio
2009-05-14 10:03     ` Charles Forsyth
     [not found] <3d5064d73b15cd2cbed06e132f419059@terzarima.net>
2009-05-14 18:29 ` lucio
2009-05-14 18:38   ` Steve Simon
2009-05-14 18:53   ` Eric Van Hensbergen
2009-05-14 19:06     ` Steve Simon
2009-05-14 19:33     ` lucio
2009-05-14 23:04     ` Charles Forsyth

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=dd6fe68a0905131500n5d846348p24c6f3bfb95264e7@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    --cc=lucio@proxima.alt.za \
    /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).