From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: Bill Fink <billfink@capu.net>
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
linuxppc-dev@lists.linuxppc.org, billfink@capu.net
Subject: Re: xine, ppc and illegal instructions
Date: Mon, 2 Apr 2001 07:50:46 -0400 [thread overview]
Message-ID: <01040207504600.17517@localhost> (raw)
In-Reply-To: <Pine.LNX.4.21.0104011709010.9900-100000@gwiz.nasa.atd.net>
Hi,
> > - could there be a cache flushing bug? When run in gdb if you set some
> > breakpoints in the shared library, it will flush the icache (to make sure
the
> > breakpoint gets flushed out of data cache and any preloaded instruction
are
> > thrown away) this in turn seems to "fix" the cache flush problem if one
> > exists.
>
> That makes sense to me.
> As reported in my previous message, it's now working using the latest
> BenH kernel (2.4.3 final) instead of the Paulus kernel (2.4.3-pre8) I
> was previously trying with, so I'm happy.
Isn't Ben's rsync kernel the one with a change in the kernel cache flushing
code?
Samuel's message said the sequence should be
stw r4,0(r2) // store instruction
dcbst 0,r2 // Flush cache
sync
icbi 0,r2
sync
isync
I have sometimes seen code where you can batch things up with multiple dcbf
and icbi before the final sync isync.
So does the batch version work properly on a 7400 series or not?
Either way, we should probably check the cache flushing code in XFree86 (it
has its own dynamic loader) and OpenOffice (bridges code uses self-modifying
code) and the ppc closures code in libffi used by gcj to flush trampolines
and whatever ever other userland code uses cache flushing because many may
have been based on the kernel version of that routine.
I will check the latter two (OpenOffice and the gcj trampoline flush) since I
have easy access to that code. Has anyone checked the XFree86 cache flushing
code?
Any info on if the flush a cache range with batched dcbf and icbi's version
used by the kernel works properly under 7400 would be greatly appreciated.
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-02 11:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0103262330001.19578-100000@gwiz.nasa.atd.net >
2001-03-27 13:41 ` xine, ppc and illegal instructions Franz Sirl
2001-04-01 17:51 ` Bill Fink
2001-04-01 19:39 ` Michel Dänzer
2001-04-01 21:08 ` Bill Fink
2001-04-01 20:02 ` Kevin B. Hendricks
2001-04-01 20:12 ` Benjamin Herrenschmidt
2001-04-01 21:24 ` Bill Fink
2001-04-02 11:50 ` Kevin B. Hendricks [this message]
2001-03-30 5:26 Henry Worth
2001-03-31 20:16 ` Bill Fink
-- strict thread matches above, loose matches on Subject: below --
2001-03-30 5:20 Henry Worth
2001-03-30 5:29 ` David Edelsohn
2001-03-30 14:59 ` Henry Worth
2001-03-27 5:30 Bill Fink
2001-03-24 19:17 Henry Worth
2001-03-24 6:13 Henry Worth
2001-03-24 4:58 Henry Worth
2001-03-24 10:57 ` Stefan Berndtsson
2001-03-23 23:53 Stefan Berndtsson
2001-03-24 0:09 ` Gregorio Gervasio Jr.
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=01040207504600.17517@localhost \
--to=khendricks@ivey.uwo.ca \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=billfink@capu.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).