From: linas <linas@austin.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: ppc64-dev <linuxppc64-dev@ozlabs.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: r13 is non-volatile?
Date: Thu, 8 Sep 2005 14:30:53 -0500 [thread overview]
Message-ID: <20050908193053.GO30028@austin.ibm.com> (raw)
In-Reply-To: <ac556638e1f4b4f9786c30ed0debc4a8@kernel.crashing.org>
On Thu, Sep 08, 2005 at 07:01:18PM +0200, Segher Boessenkool was heard to remark:
> >Was looking at merging some code between ppc32 & ppc64 and noticed
> >that in ppc32 we consider r13 to be part of the non-volatile register
> >set. Is this really correct?
>
> >r13 is suppose to be sdata pointer in ppc32
>
> sdata pointer is non-volatile by definition...
>
> >and system thread id in ppc64.
>
> The 64-bit kernel uses GPR13 as the PACA pointer, so it handles
> it specially
There's a different value in R13 depending on which cpu you're on,
so one mustn't save R13 on one CPU and attempt to restore it on
another.
Maybe, for ppc32, you can pretend that r13 "is like a paca"? So
that instead of saving/restoring r13 like this, you could set it up
at the same time/instead of setting up the paca r13?
--linas
next prev parent reply other threads:[~2005-09-08 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 16:28 r13 is non-volatile? Kumar Gala
2005-09-08 17:01 ` Segher Boessenkool
2005-09-08 19:30 ` linas [this message]
2005-09-08 21:53 ` Benjamin Herrenschmidt
2005-09-09 1:30 ` Kumar Gala
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=20050908193053.GO30028@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=segher@kernel.crashing.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).