From: Michel Lanners <mlan@cpu.lu>
To: bh40@calva.net
Cc: linuxppc-dev@lists.linuxppc.org, andre@linux-ide.org
Subject: Re: ide_delay_50ms() freezing on PPC?
Date: Thu, 29 Jun 2000 08:02:17 +0200 (CEST) [thread overview]
Message-ID: <200006290602.IAA01677@piglet.grunz.lu> (raw)
In-Reply-To: <20000627083003.23370@mailhost.mipsys.com>
Hi all,
On 27 Jun, this message from Benjamin Herrenschmidt echoed through cyberspace:
> Can you check the generated code for the loop ? Does it actually re-dead
> jiffies from memory or not ? (Did the compiler wrongly tried to optimise
> it ?).
Here is the code as it appears in vmlinux:
c00ba91c <ide_delay_50ms>:
c00ba91c: 3d 20 c0 21 lis r9,-16351
c00ba920: 81 69 c1 ec lwz r11,-15892(r9)
c00ba924: 39 6b 00 06 addi r11,r11,6
c00ba928: 80 09 c1 ec lwz r0,-15892(r9)
c00ba92c: 7d 40 58 51 subf. r10,r0,r11
c00ba930: 41 81 ff f8 bgt c00ba928 <ide_delay_50ms+0xc>
c00ba934: 4e 80 00 20 blr
I suppose r9 points to a symbol table somewhere, and the lwz loads a
specific symbol in there, which in this case should be the value of
jiffies. AFAICS, the jiffies value is thus correctly reloaded at
c00ba928. Looks OK to me, no?
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-29 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-25 18:13 ide_delay_50ms() freezing on PPC? Michel Lanners
2000-06-26 5:29 ` Andre Hedrick
2000-06-26 20:04 ` Michel Lanners
2000-06-26 20:11 ` Andre Hedrick
2000-06-27 8:30 ` Benjamin Herrenschmidt
2000-06-29 6:02 ` Michel Lanners [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=200006290602.IAA01677@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=andre@linux-ide.org \
--cc=bh40@calva.net \
--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;
as well as URLs for NNTP newsgroup(s).