9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Cc: matthiasb@acm.org
Subject: Re: [9fans] amd64 support in p9p?
Date: Thu,  2 Mar 2006 16:51:00 -0700	[thread overview]
Message-ID: <440784E4.1020400@lanl.gov> (raw)
In-Reply-To: <79a03ecc1c3386985559c25f009f1d95@swtch.com>

Russ Cox wrote:

> If the OS does not provide a working makecontext, getcontext,
> and setcontext, then you need to write those too.  They needn't
> follow any structures laid down by the rest of the system.
> They just have to match each other.  For example, power-ucontext.h
> is just made up from scratch.  It just needs to be a register set and
> match the assembly.


Also, I did not realize this when I did armv, but you needn't worry
about saving/restoring the signal mask. That really makes like easy --
no syscall needed.

ron


  reply	other threads:[~2006-03-02 23:51 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 [this message]
2006-03-02 23:56 ` Tim Wiess

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=440784E4.1020400@lanl.gov \
    --to=rminnich@lanl.gov \
    --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).