From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Arch list <linux-arch@vger.kernel.org>
Cc: "David S. Miller" <davem@redhat.com>
Subject: Changing update_mmu_cache()
Date: Tue, 22 Feb 2005 15:53:17 +1100 [thread overview]
Message-ID: <1109047997.5327.70.camel@gaston> (raw)
Hi !
I'm doing some work on the ppc32 MMU stuff and I'm faced to a problem
related to HIGHMEM, and more specifically to PTE pages in HIGHMEM:
update_mmu_cache() currently doesn't take the pte pointer. This means it
has to look it up on ppc, and eventually map the pte page (gack !). But
if you look at all the call sites for update_mmu_cache, they all have
the pte pointer and the PTE page already kmap'ed either just before or
around the call to update_mmu_cache().
My changes require me to write to the PTE (well, we already did that but
with MMU off which was sort-of ok, but my new code is different) in
update_mmu_cache().
So I want to change all call sites to pass the ptep to
update_mmu_cache() with the semantics that it will always be kmap'ed by
the caller.
Is that ok with everybody ?
Ben.
next reply other threads:[~2005-02-22 4:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 4:53 Benjamin Herrenschmidt [this message]
2005-02-22 5:43 ` Changing update_mmu_cache() David S. Miller
2005-02-22 9:07 ` Russell King
2005-02-22 18:08 ` David S. Miller
2005-02-25 20:15 ` Russell King
2005-02-25 21:43 ` Andrew Morton
2005-02-25 21:46 ` William Lee Irwin III
2005-02-25 22:48 ` Russell King
2005-02-25 22:59 ` William Lee Irwin III
2005-02-25 23:07 ` Andrew Morton
2005-02-26 1:09 ` David S. Miller
2005-02-27 18:55 ` Paul Mundt
2005-02-28 4:12 ` David S. Miller
2005-02-28 9:18 ` Paul Mundt
2005-03-06 5:15 ` David S. Miller
2005-02-27 19:27 ` Russell King
2005-02-26 1:10 ` Benjamin Herrenschmidt
2005-02-22 20:51 ` Benjamin Herrenschmidt
2005-02-23 5:35 ` Changing update_mmu_cache() or set_pte() ? Benjamin Herrenschmidt
2005-02-23 5:47 ` 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=1109047997.5327.70.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=linux-arch@vger.kernel.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