From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: <Administrator@vger.kernel.org>
Cc: "linuxppc-dev list" <linuxppc-dev@lists.linuxppc.org>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: want to clarify powerpc assembly conventions in head.Sand entry.S
Date: Sun, 11 Apr 2004 07:00:45 +0100 [thread overview]
Message-ID: <000001c41f8a$54474000$d100000a@sbs2003.local> (raw)
In-Reply-To: <4078D42C.1020608@nortelnetworks.com>
> You knew this was coming... What's special about syscalls? There's the
> r3 thing, but other than that...
The whole codepath is a bit different, there's the syscall trace,
we can avoid saving much more registers are syscalls are function
calls and so can clobber the non volatiles, etc...
> Thanks for your help with this stuff. As I've been slowly wrapping my
> head around it I've been continuously wishing for some kind of design
> rules document describing the various paths through the assembly code,
> along with register conventions and such. I eventually did find the
> conventions linked off the penguinppc website, but it was not obvious
> from just reading the code or the ppc stuff in the Documentation directory.
>
> Chris
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-11 5:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 7:41 want to clarify powerpc assembly conventions in head.S and entry.S Chris Friesen
2004-04-10 10:05 ` Benjamin Herrenschmidt
2004-04-11 5:14 ` Chris Friesen
2004-04-11 5:25 ` Benjamin Herrenschmidt
2004-04-12 14:31 ` Chris Friesen
2004-04-12 22:54 ` Benjamin Herrenschmidt
2004-04-13 4:06 ` Chris Friesen
2004-04-13 4:31 ` Chris Friesen
2004-04-12 23:30 ` want to clarify powerpc assembly conventions inhead.S " Benjamin Herrenschmidt
2004-04-12 15:01 ` want to clarify powerpc assembly conventions in head.S " Chris Friesen
2004-04-11 6:00 ` Benjamin Herrenschmidt [this message]
2004-04-11 5:45 ` Chris Friesen
2004-04-13 15:10 ` Segher Boessenkool
2004-04-13 15:45 ` Segher Boessenkool
2004-04-10 10:30 ` want to clarify powerpc assembly conventions in head.S andentry.S Benjamin Herrenschmidt
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='000001c41f8a$54474000$d100000a@sbs2003.local' \
--to=benh@kernel.crashing.org \
--cc=Administrator@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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
all inboxes | Powered by JetHome®