From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC][PATCH] [POWERPC] Allow caching of kmap_atomic page
Date: Sat, 01 Dec 2007 07:35:15 +1100 [thread overview]
Message-ID: <1196454915.13230.90.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0711300311490.1799@blarg.am.freescale.net>
On Fri, 2007-11-30 at 03:14 -0600, Kumar Gala wrote:
> Skip updating the kmap_pte and flushing the TLB if the pte we
> are about to write is the same as the one we wrote last time we
> called kmap_atomic for this km_type.
>
> Also expose the flags to allow a caller to specify their own
> flags for things like non-cacheable IO memory.
>
> ---
>
> This is the starts of some work Ben and I were discussion to allow us to
> use kmap_atomic to access a page size region of PCI CFG space when its
> provided as direct MMIO.
>
> We also intend to provide a means to preload the TLB for SW managed TLB
> machines.
We probably need to move that outside of highmem though...
Cheers,
Ben.
> - k
>
> include/asm-powerpc/highmem.h | 16 +++++++++++++---
> 1 files changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/include/asm-powerpc/highmem.h b/include/asm-powerpc/highmem.h
> index f7b21ee..a50bb00 100644
> --- a/include/asm-powerpc/highmem.h
> +++ b/include/asm-powerpc/highmem.h
> @@ -73,10 +73,12 @@ static inline void kunmap(struct page *page)
> * be used in IRQ contexts, so in some (very limited) cases we need
> * it.
> */
> -static inline void *kmap_atomic(struct page *page, enum km_type type)
> +static inline void *__kmap_atomic(struct page *page,
> + enum km_type type, unsigned long flags)
> {
> unsigned int idx;
> unsigned long vaddr;
> + pte_t pte;
>
> /* even !CONFIG_PREEMPT needs this, for in_atomic in do_page_fault */
> pagefault_disable();
> @@ -88,12 +90,20 @@ static inline void *kmap_atomic(struct page *page, enum km_type type)
> #ifdef HIGHMEM_DEBUG
> BUG_ON(!pte_none(*(kmap_pte+idx)));
> #endif
> - set_pte_at(&init_mm, vaddr, kmap_pte+idx, mk_pte(page, kmap_prot));
> - flush_tlb_page(NULL, vaddr);
> + pte = mk_pte(page, flags);
> + if (!pte_same(kmap_pte[idx], pte)) {
> + set_pte_at(&init_mm, vaddr, kmap_pte+idx, pte);
> + flush_tlb_page(NULL, vaddr);
> + }
>
> return (void*) vaddr;
> }
>
> +static inline void *kmap_atomic(struct page *page, enum km_type type)
> +{
> + return __kmap_atomic(page, type, kmap_prot);
> +}
> +
> static inline void kunmap_atomic(void *kvaddr, enum km_type type)
> {
> #ifdef HIGHMEM_DEBUG
prev parent reply other threads:[~2007-11-30 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 9:14 [RFC][PATCH] [POWERPC] Allow caching of kmap_atomic page Kumar Gala
2007-11-30 20:35 ` Benjamin Herrenschmidt [this message]
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=1196454915.13230.90.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).