From: minchan@kernel.org (Minchan Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 3/4] mm: vmalloc: add VM_DMA flag to indicate areas used by dma-mapping framework
Date: Tue, 22 May 2012 16:07:45 +0900 [thread overview]
Message-ID: <4FBB3B41.8010102@kernel.org> (raw)
In-Reply-To: <1337252085-22039-4-git-send-email-m.szyprowski@samsung.com>
On 05/17/2012 07:54 PM, Marek Szyprowski wrote:
> Add new type of vm_area intented to be used for consisten mappings
> created by dma-mapping framework.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Reviewed-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> include/linux/vmalloc.h | 1 +
> mm/vmalloc.c | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/include/linux/vmalloc.h b/include/linux/vmalloc.h
> index 6071e91..8a9555a 100644
> --- a/include/linux/vmalloc.h
> +++ b/include/linux/vmalloc.h
> @@ -14,6 +14,7 @@ struct vm_area_struct; /* vma defining user mapping in mm_types.h */
> #define VM_USERMAP 0x00000008 /* suitable for remap_vmalloc_range */
> #define VM_VPAGES 0x00000010 /* buffer for pages was vmalloc'ed */
> #define VM_UNLIST 0x00000020 /* vm_struct is not listed in vmlist */
> +#define VM_DMA 0x00000040 /* used by dma-mapping framework */
> /* bits [20..32] reserved for arch specific ioremap internals */
>
> /*
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 8cb7f22..9c13bab 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2582,6 +2582,9 @@ static int s_show(struct seq_file *m, void *p)
> if (v->flags & VM_IOREMAP)
> seq_printf(m, " ioremap");
>
> + if (v->flags & VM_DMA)
> + seq_printf(m, " dma");
> +
Hmm, VM_DMA would become generic flag?
AFAIU, maybe VM_DMA would be used only on ARM arch.
Of course, it isn't performance sensitive part but there in no reason to check it, either
in other architecture except ARM.
I suggest following as
#ifdef CONFIG_ARM
#define VM_DMA 0x00000040
#else
#define VM_DMA 0x0
#end
Maybe it could remove check code at compile time.
> if (v->flags & VM_ALLOC)
> seq_printf(m, " vmalloc");
>
--
Kind regards,
Minchan Kim
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Arnd Bergmann <arnd@arndb.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Chunsang Jeong <chunsang.jeong@linaro.org>,
Krishna Reddy <vdumpa@nvidia.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Hiroshi Doyu <hdoyu@nvidia.com>,
Subash Patel <subashrp@gmail.com>,
Nick Piggin <npiggin@gmail.com>
Subject: Re: [PATCHv2 3/4] mm: vmalloc: add VM_DMA flag to indicate areas used by dma-mapping framework
Date: Tue, 22 May 2012 16:07:45 +0900 [thread overview]
Message-ID: <4FBB3B41.8010102@kernel.org> (raw)
In-Reply-To: <1337252085-22039-4-git-send-email-m.szyprowski@samsung.com>
On 05/17/2012 07:54 PM, Marek Szyprowski wrote:
> Add new type of vm_area intented to be used for consisten mappings
> created by dma-mapping framework.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Reviewed-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> include/linux/vmalloc.h | 1 +
> mm/vmalloc.c | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/include/linux/vmalloc.h b/include/linux/vmalloc.h
> index 6071e91..8a9555a 100644
> --- a/include/linux/vmalloc.h
> +++ b/include/linux/vmalloc.h
> @@ -14,6 +14,7 @@ struct vm_area_struct; /* vma defining user mapping in mm_types.h */
> #define VM_USERMAP 0x00000008 /* suitable for remap_vmalloc_range */
> #define VM_VPAGES 0x00000010 /* buffer for pages was vmalloc'ed */
> #define VM_UNLIST 0x00000020 /* vm_struct is not listed in vmlist */
> +#define VM_DMA 0x00000040 /* used by dma-mapping framework */
> /* bits [20..32] reserved for arch specific ioremap internals */
>
> /*
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 8cb7f22..9c13bab 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2582,6 +2582,9 @@ static int s_show(struct seq_file *m, void *p)
> if (v->flags & VM_IOREMAP)
> seq_printf(m, " ioremap");
>
> + if (v->flags & VM_DMA)
> + seq_printf(m, " dma");
> +
Hmm, VM_DMA would become generic flag?
AFAIU, maybe VM_DMA would be used only on ARM arch.
Of course, it isn't performance sensitive part but there in no reason to check it, either
in other architecture except ARM.
I suggest following as
#ifdef CONFIG_ARM
#define VM_DMA 0x00000040
#else
#define VM_DMA 0x0
#end
Maybe it could remove check code at compile time.
> if (v->flags & VM_ALLOC)
> seq_printf(m, " vmalloc");
>
--
Kind regards,
Minchan Kim
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Arnd Bergmann <arnd@arndb.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Chunsang Jeong <chunsang.jeong@linaro.org>,
Krishna Reddy <vdumpa@nvidia.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Hiroshi Doyu <hdoyu@nvidia.com>,
Subash Patel <subashrp@gmail.com>,
Nick Piggin <npiggin@gmail.com>
Subject: Re: [PATCHv2 3/4] mm: vmalloc: add VM_DMA flag to indicate areas used by dma-mapping framework
Date: Tue, 22 May 2012 16:07:45 +0900 [thread overview]
Message-ID: <4FBB3B41.8010102@kernel.org> (raw)
In-Reply-To: <1337252085-22039-4-git-send-email-m.szyprowski@samsung.com>
On 05/17/2012 07:54 PM, Marek Szyprowski wrote:
> Add new type of vm_area intented to be used for consisten mappings
> created by dma-mapping framework.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Reviewed-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> include/linux/vmalloc.h | 1 +
> mm/vmalloc.c | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/include/linux/vmalloc.h b/include/linux/vmalloc.h
> index 6071e91..8a9555a 100644
> --- a/include/linux/vmalloc.h
> +++ b/include/linux/vmalloc.h
> @@ -14,6 +14,7 @@ struct vm_area_struct; /* vma defining user mapping in mm_types.h */
> #define VM_USERMAP 0x00000008 /* suitable for remap_vmalloc_range */
> #define VM_VPAGES 0x00000010 /* buffer for pages was vmalloc'ed */
> #define VM_UNLIST 0x00000020 /* vm_struct is not listed in vmlist */
> +#define VM_DMA 0x00000040 /* used by dma-mapping framework */
> /* bits [20..32] reserved for arch specific ioremap internals */
>
> /*
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 8cb7f22..9c13bab 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2582,6 +2582,9 @@ static int s_show(struct seq_file *m, void *p)
> if (v->flags & VM_IOREMAP)
> seq_printf(m, " ioremap");
>
> + if (v->flags & VM_DMA)
> + seq_printf(m, " dma");
> +
Hmm, VM_DMA would become generic flag?
AFAIU, maybe VM_DMA would be used only on ARM arch.
Of course, it isn't performance sensitive part but there in no reason to check it, either
in other architecture except ARM.
I suggest following as
#ifdef CONFIG_ARM
#define VM_DMA 0x00000040
#else
#define VM_DMA 0x0
#end
Maybe it could remove check code at compile time.
> if (v->flags & VM_ALLOC)
> seq_printf(m, " vmalloc");
>
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2012-05-22 7:07 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 10:54 [PATCHv2 0/4] ARM: replace custom consistent dma region with vmalloc Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-17 10:54 ` [PATCHv2 1/4] mm: vmalloc: use const void * for caller argument Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-22 6:58 ` Minchan Kim
2012-05-22 6:58 ` Minchan Kim
2012-05-22 6:58 ` Minchan Kim
2012-05-17 10:54 ` [PATCHv2 2/4] mm: vmalloc: export find_vm_area() function Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-22 7:01 ` Minchan Kim
2012-05-22 7:01 ` Minchan Kim
2012-05-22 7:01 ` Minchan Kim
2012-05-17 10:54 ` [PATCHv2 3/4] mm: vmalloc: add VM_DMA flag to indicate areas used by dma-mapping framework Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-22 7:07 ` Minchan Kim [this message]
2012-05-22 7:07 ` Minchan Kim
2012-05-22 7:07 ` Minchan Kim
2012-05-24 12:26 ` Marek Szyprowski
2012-05-24 12:26 ` Marek Szyprowski
2012-05-24 12:26 ` Marek Szyprowski
2012-05-24 12:28 ` Paul Mundt
2012-05-24 12:28 ` Paul Mundt
2012-05-24 12:28 ` Paul Mundt
2012-05-27 12:35 ` KOSAKI Motohiro
2012-05-27 12:35 ` KOSAKI Motohiro
2012-05-27 12:35 ` KOSAKI Motohiro
2012-05-28 8:19 ` Marek Szyprowski
2012-05-28 8:19 ` Marek Szyprowski
2012-05-28 8:19 ` Marek Szyprowski
2012-05-29 15:07 ` Konrad Rzeszutek Wilk
2012-05-29 15:07 ` Konrad Rzeszutek Wilk
2012-05-29 15:07 ` Konrad Rzeszutek Wilk
2012-05-17 10:54 ` [PATCHv2 4/4] ARM: dma-mapping: remove custom consistent dma region Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-17 10:54 ` Marek Szyprowski
2012-05-22 7:33 ` Minchan Kim
2012-05-22 7:33 ` Minchan Kim
2012-05-22 7:33 ` Minchan Kim
2012-05-22 12:50 ` Marek Szyprowski
2012-05-22 12:50 ` Marek Szyprowski
2012-05-22 12:50 ` Marek Szyprowski
2012-05-30 0:11 ` KOSAKI Motohiro
2012-05-30 0:11 ` KOSAKI Motohiro
2012-05-30 0:11 ` KOSAKI Motohiro
2012-05-30 7:15 ` Marek Szyprowski
2012-05-30 7:15 ` Marek Szyprowski
2012-05-30 7:15 ` Marek Szyprowski
2012-05-30 7:22 ` KOSAKI Motohiro
2012-05-30 7:22 ` KOSAKI Motohiro
2012-05-30 7:22 ` KOSAKI Motohiro
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=4FBB3B41.8010102@kernel.org \
--to=minchan@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.