linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Etsushi Kato <ekato@ees.hokudai.ac.jp>
To: Gabriel Paubert <paubert@iram.es>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev@lists.linuxppc.org, paulus@samba.org
Subject: Re: tlbia and PPC603
Date: Tue, 25 Jun 2002 23:43:12 +0900	[thread overview]
Message-ID: <20020625234314J.ekato@ees.hokudai.ac.jp> (raw)
In-Reply-To: <Pine.LNX.4.33.0206201256050.27936-100000@gra-lx1.iram.es>


Thank you for information, Gabriel and Ben.

I learned ppc603 software hash table some extent.  And I finally
noticed the bug in current arch/ppc/mm/ppc_mmc.c.  In old code, there
was blr at hash_page[0] and did flush_icache_range() from hash_page[0]
to hash_page[1].  But in current code, this code is removed when
comparing CPU_FT_HPTE_TABLE.

Adding this to current ppc_mmu.c have solved random crash both in
Nubus Performa and UMAX C500.  And isync before tlbie and mtsrin seems
to be not necessary.


--
Etsushi Kato
ekato@ees.hokudai.ac.jp

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-25 14:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 11:17 tlbia and PPC603 Etsushi Kato
2002-06-18 23:55 ` Benjamin Herrenschmidt
2002-06-19  3:10 ` Benjamin Herrenschmidt
2002-06-20  6:09   ` Etsushi Kato
2002-06-19  3:51     ` Benjamin Herrenschmidt
2002-06-20  7:57       ` Etsushi Kato
2002-06-20  6:36         ` Benjamin Herrenschmidt
2002-06-20 11:15   ` Gabriel Paubert
2002-06-25 14:43     ` Etsushi Kato [this message]
2002-06-24  4:02       ` Benjamin Herrenschmidt
     [not found] <20020620174254U.ekato@ees.hokudai.ac.jp>
2002-06-20  7:53 ` Benjamin Herrenschmidt
2002-06-20 10:35   ` Etsushi Kato
2002-06-20  9:12     ` Benjamin Herrenschmidt

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=20020625234314J.ekato@ees.hokudai.ac.jp \
    --to=ekato@ees.hokudai.ac.jp \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    --cc=paulus@samba.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).