linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] ARM: new cache maintenance api for iommu mem flush
Date: Wed, 20 Jun 2012 09:43:30 +0100	[thread overview]
Message-ID: <20120620084330.GA13009@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CADysL2aFufYzmxWOHp2xUt_TkqOQpX883za+7it5h2qd=PMwwA@mail.gmail.com>

On Tue, Jun 19, 2012 at 04:51:07PM +0530, Gupta, Ramesh wrote:
> >From 785a1f2854002ce7c1c8880bc5d8d92a7868bf1c Mon Sep 17 00:00:00 2001
> From: Ramesh Gupta G <grgupta@ti.com>
> Date: Fri, 15 Jun 2012 16:37:20 +0530
> Subject: [PATCH v2 1/4] ARM: new cache maintenance api for iommu mem flush
> 
> non-coherent IOMMUs need to make sure that the
> data held in the caches need to be visible for the
> MMU hardware. A new L1 cache maintenance api has been
> created to handle this. Thanks to RMK's suggestions on
> creating a dedicated API for this purpose.
> 
> ref:
> http://marc.info/?l=linux-kernel&m=131316512713815&w=2
> 
> Signed-off-by: Ramesh Gupta G <grgupta@ti.com>
> ---
>  arch/arm/include/asm/cacheflush.h |   17 +++++++++++++++++
>  arch/arm/include/asm/glue-cache.h |    1 +
>  arch/arm/mm/proc-macros.S         |    1 +
>  3 files changed, 19 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/include/asm/cacheflush.h
> b/arch/arm/include/asm/cacheflush.h
> index d5d8d5c..2b4f5aa 100644
> --- a/arch/arm/include/asm/cacheflush.h
> +++ b/arch/arm/include/asm/cacheflush.h
> @@ -84,6 +84,11 @@
>   *		- kaddr  - page address
>   *		- size   - region size
>   *
> + *     flush_mem(start, end)
> + *
> + *             Clean and invalidate the specified virtual address range.
> + *             - start  - virtual start address
> + *             - end    - virtual end address

You're missing a blank line here.

Also, "flush_mem" is a very lame name - it tells us nothing about what the
purpose of this new API is.  Should it be used for when the CPU MMU TLB
entries are changed?  What about if we're suspending, should it be used
then?  What about if we're performing DMA - should it be used for that
memory too?

Please, give it a better name which describes what it is for.

> diff --git a/arch/arm/mm/proc-macros.S b/arch/arm/mm/proc-macros.S
> index 2d8ff3a..f48a5ab 100644
> --- a/arch/arm/mm/proc-macros.S
> +++ b/arch/arm/mm/proc-macros.S
> @@ -307,6 +307,7 @@ ENTRY(\name\()_cache_fns)
>  	.long	\name\()_dma_map_area
>  	.long	\name\()_dma_unmap_area
>  	.long	\name\()_dma_flush_range
> +	.long	\name\()_flush_mem
>  	.size	\name\()_cache_fns, . - \name\()_cache_fns
>  .endm

This will immediately break the kernel compilation.  Therefore, your
patch is incomplete and unsuitable for applying.

  reply	other threads:[~2012-06-20  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 11:21 [PATCH v2 1/4] ARM: new cache maintenance api for iommu mem flush Gupta, Ramesh
2012-06-20  8:43 ` Russell King - ARM Linux [this message]
2012-06-20  9:00   ` Gupta, Ramesh

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=20120620084330.GA13009@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).