From: Richard Hirst <rhirst@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Matthew Wilcox <matthew@wil.cx>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: schedule_tail
Date: Thu, 22 Feb 2001 14:43:31 +0000 [thread overview]
Message-ID: <20010222144331.G1129@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102230114130.14557-100000@front.linuxcare.com.au>; from alan@linuxcare.com.au on Fri, Feb 23, 2001 at 01:28:36AM +1100
On Fri, Feb 23, 2001 at 01:28:36AM +1100, Alan Modra wrote:
> This is really crazy (or I am). I replaced the calls to schedule_tail
This helps for me. b,l disassembles as call, not b,l ...,rp:
===================================================================
RCS file: /home/cvs/parisc/linux/arch/parisc/kernel/entry.S,v
retrieving revision 1.72
diff -u -r1.72 entry.S
--- entry.S 2001/02/20 02:19:52 1.72
+++ entry.S 2001/02/22 14:33:43
@@ -509,7 +509,7 @@
/* Call schedule_tail first though */
- b,l schedule_tail, %r2
+ bl schedule_tail, %r2
ldo 64(%r30), %r30
ldo -64(%r30), %r30
@@ -1790,7 +1790,7 @@
/* Set the return value for the child */
child_return:
- b,l schedule_tail, %r2
+ bl schedule_tail, %r2
ldo 64(%r30), %r30
ldo -64(%r30), %r30
Richard
next prev parent reply other threads:[~2001-02-22 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0102222150310.14557-100000@front.linuxcare.com.au>
2001-02-22 14:28 ` [parisc-linux] Re: schedule_tail Alan Modra
2001-02-22 14:43 ` Richard Hirst [this message]
2001-02-22 18:24 ` Matthew Wilcox
2001-02-22 0:43 [parisc-linux] Warnings compiling the CVS kernel Helge Deller
2001-02-22 5:32 ` [parisc-linux] schedule_tail Alan Modra
2001-02-22 5:47 ` [parisc-linux] schedule_tail Matthew Wilcox
2001-02-22 6:21 ` Alan Modra
2001-02-22 6:29 ` Alan Modra
2001-02-22 6:31 ` Matthew Wilcox
2001-02-22 7:07 ` Alan Modra
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=20010222144331.G1129@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=alan@linuxcare.com.au \
--cc=matthew@wil.cx \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.