linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 8xx v2.6 TLB problems and suggested workaround
Date: Fri, 8 Apr 2005 09:39:47 -0400	[thread overview]
Message-ID: <86dfdfc8a80cde21c19c09403139ae3b@embeddededge.com> (raw)
In-Reply-To: <JPEALJAFNGDDLOPNDIEEAEHJDCAA.joakim.tjernlund@lumentis.se>


On Apr 8, 2005, at 4:01 AM, Joakim Tjernlund wrote:

> I was looking at the DTLB Error excetion(p. 7-15) in the MPC860 User's 
> Manual. There

Yeah, well what the manual says and what really happens seems to be
two different things.

> .... There is also a 8xx specific test with bit 3(0x1000000) in 
> fault.c but
> bit 3 is always zero according the MPC860 Manual for a DTLB Error.

Read the comment.  It really happens.  I spent lots and lots of time 
sorting
out how the 8xx works, setting up precise test cases and examining the
results.  Stop reading the manual too closely and create test cases to
see what exactly happens.

> Then we end up with bit 1(invalid TLB) and bit 6(store operation) set. 
> Maybe one
> could make the DTLB Error handler test if bit 1 is set and then branch 
> to
> DataAccess and then deal with the problem in fault.c?

No.  That is adding even more code to the "normal" path.  The TLB miss
should simply take a value from memory and load it into the TLB.  
Nothing
more.  It should emulate what a hardware implementation would do ...
eight instructions, no branches, if done properly :-)

Thanks.


	-- Dan

  reply	other threads:[~2005-04-08 13:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 21:51 8xx v2.6 TLB problems and suggested workaround Joakim Tjernlund
2005-04-06 12:16 ` Marcelo Tosatti
2005-04-06 21:24   ` Joakim Tjernlund
2005-04-07 12:00     ` Marcelo Tosatti
2005-04-07 20:35       ` Joakim Tjernlund
2005-04-07 19:38         ` Marcelo Tosatti
2005-04-08  2:09           ` Dan Malek
2005-04-08 11:07             ` Marcelo Tosatti
2005-04-09  5:16               ` Dan Malek
2005-04-09 19:03                 ` Joakim Tjernlund
2005-04-09 22:37                   ` Marcelo Tosatti
2005-04-10 10:08                     ` Joakim Tjernlund
2005-04-22 17:14                     ` Marcelo Tosatti
2005-04-23 21:55                   ` Dan Malek
2005-04-23 22:07                     ` Joakim Tjernlund
2005-04-23 22:23                       ` Dan Malek
2005-04-08  8:01           ` Joakim Tjernlund
2005-04-08 13:39             ` Dan Malek [this message]
2005-04-08 14:29               ` Joakim Tjernlund
  -- strict thread matches above, loose matches on Subject: below --
2005-04-04 19:17 Marcelo Tosatti
2005-04-04 20:09 ` Marcelo Tosatti
2005-04-05  7:08   ` Pantelis Antoniou
2005-04-05  1:11 ` Kumar Gala
2005-04-05 15:58 ` Dan Malek
2005-04-05 11:41   ` Marcelo Tosatti
2005-04-05 20:26     ` Marcelo Tosatti
2005-04-06  6:00   ` Pantelis Antoniou

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=86dfdfc8a80cde21c19c09403139ae3b@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=linuxppc-embedded@ozlabs.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).