mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.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.S	and	entry.S
Date: Tue, 13 Apr 2004 00:06:14 -0400	[thread overview]
Message-ID: <407B6736.9090607@nortelnetworks.com> (raw)
In-Reply-To: <1081810459.1401.212.camel@gaston>

Benjamin Herrenschmidt wrote:

> ret_from_syscall for syscalls, hash_page also has a different
> return to userland path, and load_up_{fpu,altivec} have their own
> retturn path.
> On ppc32 currently, the entry is almost always the same except for
> hash_page and load_up_{fpu,altivec}

Thanks, that's exactly the information I needed.

Chris

  reply	other threads:[~2004-04-13  4:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  7:41 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 [this message]
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     ` want to clarify powerpc assembly conventions in head.Sand entry.S Benjamin Herrenschmidt
2004-04-11  5:45   ` want to clarify powerpc assembly conventions in head.S and entry.S 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=407B6736.9090607@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=benh@kernel.crashing.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®