Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Phil Schwan <pschwan@thepuffingroup.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] [prumpf@jcsbs.lanobis.de: temporary registers]
Date: Fri, 30 Apr 1999 01:50:03 -0400	[thread overview]
Message-ID: <19990430015003.E20143@cmu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 334 bytes --]

This mail was sent while I was moving the mailing lists to their new
home.  I apologise for the delay.

-Phil

------------------------------------------------------------------
"In film you will find four basic story lines. Man versus man, man
versus nature, nature versus nature, and dog versus vampire."
        - Steven Spielberg

[-- Attachment #2: Forwarded message from Philipp Rumpf <prumpf@jcsbs.lanobis.de> --]
[-- Type: message/rfc822, Size: 2264 bytes --]

From: Philipp Rumpf <prumpf@jcsbs.lanobis.de>
To: parisc-linux@thepuffingroup.com
Subject: temporary registers
Date: Thu, 29 Apr 1999 16:50:05 +0000
Message-ID: <19990429165005.06165@insula.local>

I am currently trying to get basic kernel stuff for the pa1.1 port to work.
We have 6 temporary registers that are read/writable by PL0-code only. I
think we should use them to save commonly used values to have them ready
in interrupt handlers.

I propose to use them in the following way:

CR24 - current, 0 while we are handling an interruption
	current is where the registers' contents are stored when we enter
an interruption handler. We have to set it to some "special value" when we
already use the register save slots in current so we don't overwrite them.
(we can save the registers on the kernel stack in that case).

CR30 - kernel stack pointer, 0 when we are using the kernel stack
	when this is 0, GR30 is the valid kernel stack pointer

CR31 - kernel global pointer

this leaves us 3 more registers to save the registers in to handle inter-
ruptions.

	Philipp

                 reply	other threads:[~1999-04-30  5:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19990430015003.E20143@cmu.edu \
    --to=pschwan@thepuffingroup.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