linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/9] ARM: Remove superfluous flush_kernel_dcache_page()
Date: Tue, 31 Aug 2010 14:58:29 +0100	[thread overview]
Message-ID: <20100831135829.21304.99094.stgit@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <20100831135435.21304.38960.stgit@e102109-lin.cambridge.arm.com>

Since page cache pages are now considered 'dirty' by default, the cache
flushing is handled via __flush_dcache_page() when a page gets mapped to
user space. Highmem pages on VIVT systems are flushed during kunmap()
and flush_kernel_dcache_page() was already a no-op in this case.

ARCH_HAS_FLUSH_KERNEL_DCACHE_PAGE is still defined since ARM needs
specific implementations for flush_kernel_vmap_range() and
invalidate_kernel_vmap_range().

Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
---
 arch/arm/include/asm/cacheflush.h |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/arch/arm/include/asm/cacheflush.h b/arch/arm/include/asm/cacheflush.h
index d3730f0..042e139 100644
--- a/arch/arm/include/asm/cacheflush.h
+++ b/arch/arm/include/asm/cacheflush.h
@@ -405,9 +405,6 @@ static inline void flush_anon_page(struct vm_area_struct *vma,
 #define ARCH_HAS_FLUSH_KERNEL_DCACHE_PAGE
 static inline void flush_kernel_dcache_page(struct page *page)
 {
-	/* highmem pages are always flushed upon kunmap already */
-	if ((cache_is_vivt() || cache_is_vipt_aliasing()) && !PageHighMem(page))
-		__cpuc_flush_dcache_area(page_address(page), PAGE_SIZE);
 }
 
 #define flush_dcache_mmap_lock(mapping) \

  parent reply	other threads:[~2010-08-31 13:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 13:57 [PATCH 0/9] Various patches for 2.6.37-rc1 Catalin Marinas
2010-08-31 13:58 ` [PATCH 1/9] ARM: Allow lazy cache flushing via PG_arch_1 for highmem pages Catalin Marinas
2010-08-31 13:58 ` [PATCH 2/9] ARM: Assume new page cache pages have dirty D-cache Catalin Marinas
2010-08-31 13:58 ` [PATCH 3/9] ARM: Introduce __sync_icache_dcache() for VIPT caches Catalin Marinas
2010-08-31 13:58 ` [PATCH 4/9] ARM: Use lazy cache flushing on ARMv7 SMP systems Catalin Marinas
2010-08-31 13:58 ` Catalin Marinas [this message]
2010-08-31 13:58 ` [PATCH 6/9] ARM: Implement phys_mem_access_prot() to avoid attributes aliasing Catalin Marinas
2010-08-31 13:58 ` [PATCH 7/9] ARM: Improve the L2 cache performance when PL310 is used Catalin Marinas
2010-09-13 11:36   ` Russell King - ARM Linux
2010-09-13 11:57     ` Catalin Marinas
2010-08-31 13:58 ` [PATCH 8/9] ARM: Remove the domain switching on ARMv6k/v7 CPUs Catalin Marinas
2010-08-31 13:58 ` [PATCH 9/9] ARM: Add SWP/SWPB emulation for ARMv7 processors (v5) Catalin Marinas
2010-08-31 15:05   ` Kirill A. Shutemov
2010-09-06 15:42     ` Catalin Marinas
2010-09-13 11:55       ` Russell King - ARM Linux
2010-09-14 13:50         ` Leif Lindholm
2010-09-01  4:08   ` Olof Johansson
2010-09-02 17:04     ` Leif Lindholm
2010-09-02 17:20       ` Olof Johansson

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=20100831135829.21304.99094.stgit@e102109-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).