From: benh@kernel.crashing.org
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Dan Malek <dan@embeddededge.com>,
Paul Mackerras <paulus@samba.org>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: More details on the telnet with CONFIG_PIN_TLB problems
Date: Tue, 4 Jun 2002 21:31:30 +0200 [thread overview]
Message-ID: <20020604193130.2384@mailhost.mipsys.com> (raw)
In-Reply-To: <20020605032241.GD2630@zax>
>I've committed a patch to use 'sync' before changing the PID (to flush
>any loads/stores through the MMU before we change the context) and
>'isync' afterwards to flush the shadow TLBs. I'm guessing that isync
>flushes both shadow TLBs, not just the ITLB, and that the missing
>infomation is a documentation error. I've sent some email to the IBM
>PPC support people to check.
Sounds good. In my local tree, I also replaced the icbi's in
flush_dcache_icache & flush_instruction_cache with iccci's to
make sure we don't have stale aliases. I haven't yet checked
glibc for this though.
Ben.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-04 19:31 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
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 [this message]
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=20020604193130.2384@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=dan@embeddededge.com \
--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).