From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: <khendricks@ivey•uwo.ca>
Cc: <linuxppc-dev@lists•linuxppc.org>, <billfink@capu•net>
Subject: Re: xine, ppc and illegal instructions
Date: Sun, 1 Apr 2001 22:12:53 +0200 [thread overview]
Message-ID: <20010401201253.17215@smtp.wanadoo.fr> (raw)
In-Reply-To: <01040116021700.15950@localhost>
>- 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.
Franz and I checked glibc for the cache flushing problem reported by
Samuel Rydth and it's ok. However, the kernel did miss those sync's.
I can't tell if it's the cause of the problem, however, my rsync kernel
have those changes. I'll push them to bk soon.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-01 20:12 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 [this message]
2001-04-01 21:24 ` Bill Fink
2001-04-02 11:50 ` Kevin B. Hendricks
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=20010401201253.17215@smtp.wanadoo.fr \
--to=benh@kernel$(echo .)crashing.org \
--cc=billfink@capu$(echo .)net \
--cc=khendricks@ivey$(echo .)uwo.ca \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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