From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 4 Jun 2002 17:34:02 -0700 From: Matt Porter To: david@gibson.dropbear.id.au, Paul Mackerras , linuxppc-embedded@lists.linuxppc.org Subject: Re: More details on the telnet with CONFIG_PIN_TLB problems Message-ID: <20020604173402.A15690@home.com> References: <20020603075322.GI6765@zax> <15612.47259.378190.93509@argo.ozlabs.ibm.com> <20020604095720.A15252@home.com> <20020605000239.GA17752@zax> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20020605000239.GA17752@zax>; from david@gibson.dropbear.id.au on Wed, Jun 05, 2002 at 10:02:39AM +1000 Sender: owner-linuxppc-embedded@lists.linuxppc.org List-Id: On Wed, Jun 05, 2002 at 10:02:39AM +1000, David Gibson wrote: > > On Tue, Jun 04, 2002 at 09:57:20AM -0700, Matt Porter wrote: > > > > On Tue, Jun 04, 2002 at 10:54:51PM +1000, Paul Mackerras wrote: > > > > > > Looks like Ben and I have found the problem; Ben added an isync and a > > > sync to set_context() after setting the PID register and that seems to > > > have fixed it. It makes sense, as isync invalidates the shadow DTLB > > > and ITLB. (The sync may be unnecessary.) > > > > Makes sense, I was telling some folks at work that it had to be a > > 40x specific code problem. The 440 has had an isync in set_context() > > and doesn't see this problem (and by default uses pinned TLBs). > > Heh, well not only uses them by default, but must use them since > translation is always on. Heh, I should have said, "and by design, must use . . .". ;) Regards, -- Matt Porter porter@cox.net This is Linux Country. On a quiet night, you can hear Windows reboot. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/