From: Matt Porter <porter@cox.net>
To: Paul Mackerras <paulus@samba.org>
Cc: David Gibson <david@gibson.dropbear.id.au>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: More details on the telnet with CONFIG_PIN_TLB problems
Date: Tue, 4 Jun 2002 09:57:20 -0700 [thread overview]
Message-ID: <20020604095720.A15252@home.com> (raw)
In-Reply-To: <15612.47259.378190.93509@argo.ozlabs.ibm.com>; from paulus@samba.org on Tue, Jun 04, 2002 at 10:54:51PM +1000
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).
Changing the PID is a context changing event that requires a context
synchronization. The sync shouldn't be necessary per the UM and
seems to be true in practice from my 440 testing.
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/
next prev parent reply other threads:[~2002-06-04 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 7:53 More details on the telnet with CONFIG_PIN_TLB problems David Gibson
2002-06-04 12:54 ` Paul Mackerras
2002-06-04 14:39 ` David Gibson
2002-06-04 16:57 ` Matt Porter [this message]
2002-06-05 0:02 ` David Gibson
2002-06-05 0:34 ` Matt Porter
2002-06-04 17:04 ` Dan Malek
2002-06-04 16:43 ` Benjamin Herrenschmidt
2002-06-05 3:22 ` David Gibson
2002-06-04 19:31 ` benh
2002-06-06 1:42 ` David Gibson
2002-06-05 22:15 ` Benjamin Herrenschmidt
2002-06-06 7:52 ` David Gibson
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=20020604095720.A15252@home.com \
--to=porter@cox.net \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--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).