From: Kumar Gala <galak@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: SW TLB MMU rework and SMP issues
Date: Tue, 15 Jul 2008 16:58:16 -0500 [thread overview]
Message-ID: <BF59BFC7-736B-4D3F-9227-97DC90CE4739@kernel.crashing.org> (raw)
Ben,
I've been giving some thought to the new software managed TLBs and SMP
issues. I was wondering if you had any insights on how we should deal
with the following issues:
* tlb invalidates -- need to ensure we don't have multiple tlbsync's
on the bus. I'm thinking for e500/fsl we will move to IPI based
invalidate broadcast and do invalidates locally (http://patchwork.ozlabs.org/linuxppc/patch?id=19657
)
* 64-bit PTEs and reader vs writer hazards. How do we ensure that the
TLB miss handler samples a consistent view of the pte. pte_updates
seem ok since we only update the flag word. However set_pte_at seems
like it could be problematic.
- k
next reply other threads:[~2008-07-15 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 21:58 Kumar Gala [this message]
2008-07-16 2:07 ` SW TLB MMU rework and SMP issues Benjamin Herrenschmidt
2008-07-16 20:57 ` SW TLB MMU rework and SMP issues (pte read/write) Kumar Gala
2008-07-16 21:15 ` Kumar Gala
2008-07-16 21:41 ` Benjamin Herrenschmidt
2008-07-16 22:12 ` Kumar Gala
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=BF59BFC7-736B-4D3F-9227-97DC90CE4739@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).