Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Florian Lohoff <flo@rfc822.org>,
	linux-mips@linux-mips.org, debian-mips@lists.debian.org
Subject: Re: Tester with IP27/IP30 needed
Date: Fri, 25 Jan 2008 22:12:50 -0500	[thread overview]
Message-ID: <479AA532.5040603@gentoo.org> (raw)
In-Reply-To: <20080122154958.GA29108@linux-mips.org>

Ralf Baechle wrote:
> 
> It's a cache instruction so priviledged which means userspace can't execute
> it.  It's also entirely unclear if a cache barrier instruction would make a
> difference at all.

The cache barrier has an interesting effect.  I built three binaries: f, f2, and 
f3 (I'm cheap on the names):

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 running on 
2.6.23.9, using Thomas' patches backported to fit (plus Peter's Impact code and 
two sgiseeq patches from upstream).

This is similar to using a gentoo stage3 in a chroot environment that was built 
back in May of 2007, so I think this hang up pre-dates glibc-2.7 by some degree, 
as that chroot uses glibc-2.5.  Chroot into this userland, and run our 
"env-update" script, and you'll hang the box.

FYI, CPU rev in this machine is R10000 v2.5.  I think that's the same for all 
IP28 systems.



--Kumba

-- 
Gentoo/MIPS Team Lead

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

  reply	other threads:[~2008-01-26  3:13 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 [this message]
2008-01-26 14:39           ` Thomas Bogendoerfer
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=479AA532.5040603@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=debian-mips@lists.debian.org \
    --cc=flo@rfc822.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tsbogend@alpha.franken.de \
    /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