linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: linux-arch@vger.kernel.org
Cc: linux-parisc@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Russell King <rmk@arm.linux.org.uk>,
	Paul Mundt <lethal@linux-sh.org>,
	James Bottomley <James.Bottomley@suse.de>
Subject: [PATCHv2 2/5] parisc: add mm API for DMA to vmalloc/vmap areas
Date: Wed, 23 Dec 2009 15:22:22 -0600	[thread overview]
Message-ID: <1261603345-2494-3-git-send-email-James.Bottomley@suse.de> (raw)
In-Reply-To: <1261603345-2494-2-git-send-email-James.Bottomley@suse.de>

We already have an API to flush a kernel page along an alias
address, so use it.  The TLB purge prevents the CPU from doing
speculative moveins on the flushed address, so we don't need to
implement and invalidate.

Signed-off-by: James Bottomley <James.Bottomley@suse.de>
---
 arch/parisc/include/asm/cacheflush.h |   12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/arch/parisc/include/asm/cacheflush.h b/arch/parisc/include/asm/cacheflush.h
index 7a73b61..4772777 100644
--- a/arch/parisc/include/asm/cacheflush.h
+++ b/arch/parisc/include/asm/cacheflush.h
@@ -38,6 +38,18 @@ void flush_cache_mm(struct mm_struct *mm);
 
 #define flush_kernel_dcache_range(start,size) \
 	flush_kernel_dcache_range_asm((start), (start)+(size));
+/* vmap range flushes and invalidates.  Architecturally, we don't need
+ * the invalidate, because the CPU should refuse to speculate once an
+ * area has been flushed, so invalidate is left empty */
+static inline void flush_kernel_vmap_range(void *vaddr, int size)
+{
+	unsigned long start = (unsigned long)vaddr;
+
+	flush_kernel_dcache_range_asm(start, start + size);
+}
+static inline void invalidate_kernel_vmap_range(void *vaddr, int size)
+{
+}
 
 #define flush_cache_vmap(start, end)		flush_cache_all()
 #define flush_cache_vunmap(start, end)		flush_cache_all()
-- 
1.6.5

  parent reply	other threads:[~2009-12-23 21:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 21:22 [PATCHv2 0/5] fix xfs by making I/O to vmap/vmalloc areas work James Bottomley
2009-12-23 21:22 ` [PATCHv2 1/5] mm: add coherence API for DMA to vmalloc/vmap areas James Bottomley
2009-12-23 21:22   ` James Bottomley
2009-12-23 21:22   ` James Bottomley [this message]
2009-12-23 21:22     ` [PATCHv2 3/5] arm: add mm " James Bottomley
2009-12-23 21:22       ` [PATCHv2 4/5] sh: " James Bottomley
2009-12-23 21:22         ` James Bottomley
2009-12-23 21:22         ` [PATCHv2 5/5] xfs: fix xfs to work with Virtually Indexed architectures James Bottomley
2009-12-24 11:03           ` Christoph Hellwig
2009-12-24 11:03             ` Christoph Hellwig
2009-12-27 15:32             ` James Bottomley
2010-01-02 21:33     ` [PATCHv2 2/5] parisc: add mm API for DMA to vmalloc/vmap areas Benjamin Herrenschmidt
2010-01-02 21:33       ` Benjamin Herrenschmidt
2010-01-02 21:53       ` James Bottomley
2010-01-03 20:12         ` Benjamin Herrenschmidt
2010-01-03 20:12           ` Benjamin Herrenschmidt
2009-12-24 10:08   ` [PATCHv2 1/5] mm: add coherence " Matt Fleming
2009-12-24 10:08     ` Matt Fleming
2009-12-24 12:39     ` Matthew Wilcox
2009-12-24 12:39       ` Matthew Wilcox
2009-12-24 13:06       ` Matt Fleming
2009-12-24 13:06         ` Matt Fleming
2009-12-27 15:37       ` James Bottomley
2010-01-02 21:27       ` Benjamin Herrenschmidt
2010-01-02 21:54         ` James Bottomley
2010-01-03 20:14           ` Benjamin Herrenschmidt
2010-01-03 20:14             ` 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=1261603345-2494-3-git-send-email-James.Bottomley@suse.de \
    --to=james.bottomley@suse.de \
    --cc=hch@lst.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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).