From: Tim Wiess <tim@nop.cx>
To: matthiasb@acm.org
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] amd64 support in p9p?
Date: Thu, 2 Mar 2006 15:56:31 -0800 [thread overview]
Message-ID: <7674f1c1d1b88693bd56a6100c1c6fef@akira.nop.cx> (raw)
In-Reply-To: <20060302231511.GA11050@pestilenz.org>
on OpenBSD you'll need to copy over rfork_thread and roll
your own {get,set}context functions. however as Russ mentioned,
you don't really need to use OpenBSD's ucontext_t (sigcontext)
for this.
tim
> Hi all,
> is there anybody interested in helping to port the
> plan9 from user space to amd64/x86_64?
> The most platform dependend code seems to be the libthread
> stuff. On OpenBSD-amd64 I can borrow an assembler version of
> rfork_thread from the OpenBSD librthread and can improvise
> the _tas function. The get/setmcontext pose a problem because
> I do not know if struct ucontext must really be exactly the same
> as struct sigcontext.
>
> Best regards,
>
> Matthias
prev parent reply other threads:[~2006-03-02 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 23:15 plan9
2006-03-02 23:23 ` Devon H. O'Dell
2006-03-02 23:27 ` Russ Cox
2006-03-02 23:51 ` Ronald G Minnich
2006-03-02 23:56 ` Tim Wiess [this message]
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=7674f1c1d1b88693bd56a6100c1c6fef@akira.nop.cx \
--to=tim@nop.cx \
--cc=9fans@cse.psu.edu \
--cc=matthiasb@acm.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;
as well as URLs for NNTP newsgroup(s).