From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Kumba <kumba@gentoo.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Florian Lohoff <flo@rfc822.org>,
linux-mips@linux-mips.org, debian-mips@lists.debian.org
Subject: Re: Tester with IP27/IP30 needed
Date: Sat, 26 Jan 2008 15:39:49 +0100 [thread overview]
Message-ID: <20080126143949.GA6579@alpha.franken.de> (raw)
In-Reply-To: <479AA532.5040603@gentoo.org>
On Fri, Jan 25, 2008 at 10:12:50PM -0500, Kumba wrote:
> f - cache barriers on load and stores (-mr10k-cache-barrier=2)
> f2 - cache barriers on loads only (-mr10k-cache-barrier=1)
> f3 - no cache barriers (flag omitted from gcc)
>
> Running 'f' and 'f2' generates an "Illegal instruction" error, then drops
> back to the command line, while 'f3' hangs the box. This is an IP28
no suprise here. As Ralf already noted cache barrier is a restricted
instruction, it will always cause a illegal instruction when used
in user space. Nevertheless it looks like all IP28 are affected
by the simple exploit. Flo built glibc 2.7 with LLSC war workaround
and this avoids triggering the hang.
> FYI, CPU rev in this machine is R10000 v2.5. I think that's the same for
> all IP28 systems.
Flo and mine also have rev 2.5 cpus.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2008-01-26 14:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 11:24 Tester with IP27/IP30 needed Thomas Bogendoerfer
2008-01-15 11:27 ` Florian Lohoff
2008-01-17 0:40 ` Thomas Bogendoerfer
2008-01-17 8:27 ` Florian Lohoff
2008-01-17 10:00 ` Thomas Bogendoerfer
2008-01-17 15:10 ` Ralf Baechle
2008-01-19 19:12 ` Thomas Bogendoerfer
2008-01-17 11:59 ` Ralf Baechle
2008-01-22 15:20 ` Kumba
2008-01-22 15:49 ` Ralf Baechle
2008-01-26 3:12 ` Kumba
2008-01-26 14:39 ` Thomas Bogendoerfer [this message]
2008-02-02 22:08 ` Kumba
2008-02-03 2:16 ` Ralf Baechle
2008-02-03 6:27 ` Florian Lohoff
2008-02-05 7:11 ` Kumba
2008-02-05 12:22 ` Thiemo Seufer
2008-02-06 3:25 ` Kumba
2008-02-06 8:56 ` Florian Lohoff
2008-02-06 14:22 ` Ralf Baechle
2008-02-08 17:23 ` Florian Lohoff
2008-02-08 19:05 ` Thiemo Seufer
2008-02-08 19:29 ` Ralf Baechle
2008-02-07 5:30 ` Kumba
2008-02-05 15:23 ` Ralf Baechle
2008-01-23 8:47 ` peter fuerst
2008-01-15 13:11 ` Ralf Baechle
2008-01-15 13:53 ` Ralf Baechle
2008-01-15 18:18 ` Ralf Baechle
2008-01-16 16:03 ` Ralf Baechle
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=20080126143949.GA6579@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=debian-mips@lists.debian.org \
--cc=flo@rfc822.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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