From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] static registers during a context switch
Date: Wed, 25 Oct 2000 14:28:06 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205624@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205620@msgid-missing>
If you are thinking of a context switch in the sense of switching
from one process to another then ALL registers, static and stacked,
are saved and restored. If you are talking about making a subroutine
call then the uses of the static registers are covered by software
convention and registers R4-R7 are preserved across a function call.
Conceptually the static registers are similar to the X86 registers
EAX, EBX and so on. These registers are also saved and restored
across context switches and have software conventions that control
which ones are saved across subroutine calls.
On Tue, Oct 24, 2000 at 09:47:41PM -0500, riedel wrote:
> hi everybody,
> does anybody know what happens to static registers (gr0-gr31) in case of a context switch.
> in the manual, it says static registers are visible to all procedures(i guess it shouldn't otherwise on a context switch another process would have the same static registers) On the other hand, stacked registers are local to procedures and saved and restored by RSE which makes sense to me.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838
prev parent reply other threads:[~2000-10-25 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-25 2:47 [Linux-ia64] static registers during a context switch riedel
2000-10-25 10:16 ` Doug Rabson
2000-10-25 14:28 ` Don Dugger [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=marc-linux-ia64-105590678205624@msgid-missing \
--to=n0ano@valinux.com \
--cc=linux-ia64@vger.kernel.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