From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Dan Malek" <dan@embeddededge.com>
Cc: "Tom Rini" <trini@kernel.crashing.org>,
"Linuxppc-Embedded@Lists. Linuxppc. Org"
<linuxppc-embedded@lists.linuxppc.org>,
<strauman@SLAC.Stanford.EDU>
Subject: Re: dcbz works on 862 everywhere!
Date: Tue, 25 Mar 2003 01:33:47 +0100 [thread overview]
Message-ID: <002501c2f266$3626e5a0$020120b0@jockeXP> (raw)
In-Reply-To: 3E7F8DE4.1040901@embeddededge.com
> Joakim Tjernlund wrote:
>
> >
> > I think it makes the "copy DAR to MD_EPN" part in the DTLB error handler needless.
> > Anyway it works with and without that part.
>
> No, you need to leave that there as well. Read the comment.....
>
> If it appears to "work" for you, what happens is you have a DTLB Error
> immediately following a DTLB miss (the common case lots of the time), so
> the MD_EPN just happens to contain the proper information. When you generate
> the case where a DTLB Error does not match a previous DTLB miss, you will
> end up tracking down the wrong PTEs. Even in this case it is likely to
> appear things work correctly, but they do not. There is one case with the dcbi
> where there is no proper operation of the code, so it was necessary to solve
> the problem another way.
What case is that(when dcbi does not work)? Give me an example so I can test
and see what happens, with and without my patch.
> This is exactly why people are telling you to carefully generate test cases
> the prove an error exists 100% of the time, and that your modifications
> properly correct the condition 100% of the time. When you run something
> like Linux you get pathological cases that do not exercise all conditions
> with a particular configurations, or you could be generating errors that
> are not precisely tested as failure conditions.
I know all that and thats why post to the list with questions, ideas and patches to try out.
If you had read my mails you would had understood that too.
Your yelling at me for trying isn't very helpful.
Jocke
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-25 0:33 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 10:19 dcbz works on 862 everywhere! Joakim Tjernlund
2003-03-24 11:01 ` Joakim Tjernlund
2003-03-24 12:25 ` Joakim Tjernlund
2003-03-24 14:20 ` Joakim Tjernlund
2003-03-24 17:09 ` Till Straumann
2003-03-24 17:42 ` Joakim Tjernlund
2003-03-24 20:15 ` Tom Rini
2003-03-24 20:57 ` Joakim Tjernlund
2003-03-24 21:07 ` Tom Rini
2003-03-24 21:54 ` Joakim Tjernlund
2003-03-24 22:59 ` Dan Malek
2003-03-25 0:33 ` Joakim Tjernlund [this message]
2003-03-24 21:42 ` Dan Malek
2003-03-24 21:51 ` Joakim Tjernlund
2003-03-24 22:44 ` Joakim Tjernlund
2003-03-24 23:09 ` Dan Malek
2003-03-24 23:57 ` Joakim Tjernlund
2003-03-25 0:48 ` Dan Malek
2003-03-25 1:22 ` Dan Malek
2003-03-25 14:02 ` Joakim Tjernlund
2003-03-26 2:17 ` Till Straumann
2003-03-26 7:57 ` Joakim Tjernlund
2003-03-26 15:18 ` Dan Malek
2003-03-26 17:04 ` Joakim Tjernlund
2003-03-26 18:52 ` Dan Malek
2003-03-27 21:49 ` Joakim Tjernlund
2003-03-26 18:11 ` Till Straumann
2003-03-26 19:06 ` Dan Malek
2003-03-26 22:42 ` mpc8xx DCBZ (&friends) hw bug. Tests, analysis + conclusions Till Straumann
2003-03-27 1:25 ` Till Straumann
2003-03-27 14:01 ` Joakim Tjernlund
2003-04-03 12:50 ` Joakim Tjernlund
2003-04-08 10:47 ` Joakim Tjernlund
2003-04-08 16:25 ` Till Straumann
2003-04-08 16:42 ` Joakim Tjernlund
2003-04-08 16:52 ` Joakim Tjernlund
2003-04-08 21:01 ` Dan Malek
2003-04-08 17:25 ` Joakim Tjernlund
2003-04-08 18:14 ` Tom Rini
2003-04-08 21:07 ` Joakim Tjernlund
2003-05-09 12:37 ` Joakim Tjernlund
2003-04-01 9:37 ` dcbz works on 862 everywhere! Joakim Tjernlund
2003-04-04 15:09 ` Joakim Tjernlund
2003-04-04 15:43 ` Dan Malek
2003-04-04 16:37 ` Joakim Tjernlund
2003-04-09 14:32 ` Joakim Tjernlund
2003-03-26 18:52 ` Till Straumann
2003-03-25 1:57 ` Joakim Tjernlund
2003-03-25 17:37 ` Joakim Tjernlund
2003-03-26 15:22 ` Dan Malek
2003-03-26 17:09 ` Joakim Tjernlund
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='002501c2f266$3626e5a0$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=strauman@SLAC.Stanford.EDU \
--cc=trini@kernel.crashing.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).