From: LaMont Jones <lamont@security.hp.com>
To: Matthew Wilcox <Matthew.Wilcox@genedata.com>
Cc: LaMont Jones <lamont@security.hp.com>,
parisc-linux@thepuffingroup.com, lamont@security.hp.com
Subject: Re: [parisc-linux] xchg implementation
Date: Tue, 02 Nov 1999 07:10:58 -0700 [thread overview]
Message-ID: <19991102141105.9EB1518708@security.hp.com> (raw)
In-Reply-To: Your message of "Tue, 02 Nov 1999 09:53:40 +0100." <19991102095340.D516@mencheca.ch.genedata.com>
> > IIRC, CR24 and 25 are readable from user space (not writable), and can be
> > quite useful for thread specific data, thread id, etc... It might do to
> > leave them available for such a use.
> You're thinking of CR26 and 27 (ref: Kane's PA-RISC 2.0 Architecture,
> page 2-17). CR31 _is_ used, I didn't read carefully enough:
And the worst of it is that I knew that. Sigh...
thanks for the clarification,
lamont
next prev parent reply other threads:[~1999-11-02 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-31 18:37 [parisc-linux] xchg implementation Matthew Wilcox
1999-11-01 21:03 ` LaMont Jones
1999-11-02 8:53 ` Matthew Wilcox
1999-11-02 14:10 ` LaMont Jones [this message]
1999-11-06 19:22 ` Philipp Rumpf
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=19991102141105.9EB1518708@security.hp.com \
--to=lamont@security.hp.com \
--cc=Matthew.Wilcox@genedata.com \
--cc=parisc-linux@thepuffingroup.com \
/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