Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: Hanging.
Date: Fri, 1 May 1998 12:45:48 -0700	[thread overview]
Message-ID: <199805011945.MAA23172@fir.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.3.95.980501153605.22853E-100000@lager.engsoc.carleton.ca>

Alex deVries writes:
 > 
 > On Fri, 1 May 1998, William J. Earl wrote:
 > >      Is this an R4000?  If so, it might be the count/compare erratum, if
 > > the linux kernel does not have the workaround for it yet.  (I haven't
 > > checked the linux sources.)
 > 
 > This is an R4600.  How would I check if there were that patch applied?

     The problem I have in mind cannot occur on an R4600.  The modification
is to the routine which fetches $count.  On the R4000, if you are depending
on the $compare match interrupt, you have to check for the possibility
that $count equalled $compare when you fetched it, since that causes
the interrupt to not happen.  In that case, you have to fake the
interrupt in some way, or have to wait for $count to wrap (about 84 seconds
at 100 MHZ).  IRIX just checks to see if the fetched copy of $count
is close to a shadow copy $compare.  If it is, and if the clock interrupt
request bit is off (this being done with interrupts disabled), we
set $compare a little head of the current $count and spin until the
interrupt bit goes on (with some care to avoid getting stuck if we
lose the race in terms of setting $compare ahead of $count).  Again,
all this only applies to the R4000, not to the R4400, R4600, or R5000.

  reply	other threads:[~1998-05-01 19:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-01 18:20 Hanging Alex deVries
1998-05-01 19:29 ` Hanging William J. Earl
1998-05-01 19:37   ` Hanging Alex deVries
1998-05-01 19:45     ` William J. Earl [this message]
1998-05-02 10:52 ` Hanging ralf
1998-05-03  1:26   ` Hanging Alex deVries
1998-05-03 18:22   ` Hanging Alex deVries
1998-05-03 18:40     ` Hanging ralf
1998-05-04  2:15       ` Hanging Alex deVries
1998-05-04  6:57         ` Hanging ralf
1998-05-04 17:14           ` Hanging Alex deVries
1998-05-04 19:32             ` Hanging ralf
1998-05-04 19:45               ` Hanging Alex deVries

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=199805011945.MAA23172@fir.engr.sgi.com \
    --to=wje@fir.engr.sgi.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.com \
    /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