From: Marek Szyprowski <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Hiroshi Doyu <hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linaro-mm-sig-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
chunsang.jeong-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
vdumpa-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
subashrp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
minchan-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
pullip.cho-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [v4 0/4] ARM: dma-mapping: IOMMU atomic allocation
Date: Tue, 28 Aug 2012 18:51:00 +0200 [thread overview]
Message-ID: <503CF6F4.7060702@samsung.com> (raw)
In-Reply-To: <1346130784-23571-1-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Hello,
On 8/28/2012 7:13 AM, Hiroshi Doyu wrote:
> The commit e9da6e9 "ARM: dma-mapping: remove custom consistent dma
> region" breaks the compatibility with existing drivers. This causes
> the following kernel oops(*1). That driver has called dma_pool_alloc()
> to allocate memory from the interrupt context, and it hits
> BUG_ON(in_interrpt()) in "get_vm_area_caller()". This patch seris
> fixes this problem with making use of the pre-allocate atomic memory
> pool which DMA is using in the same way as DMA does now.
>
> Any comment would be really appreciated.
Looks fine now. I will do some tests and apply them to my fixes-for-3.6
branch. Thanks for Your contribution!
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
WARNING: multiple messages have this Message-ID (diff)
From: m.szyprowski@samsung.com (Marek Szyprowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [v4 0/4] ARM: dma-mapping: IOMMU atomic allocation
Date: Tue, 28 Aug 2012 18:51:00 +0200 [thread overview]
Message-ID: <503CF6F4.7060702@samsung.com> (raw)
In-Reply-To: <1346130784-23571-1-git-send-email-hdoyu@nvidia.com>
Hello,
On 8/28/2012 7:13 AM, Hiroshi Doyu wrote:
> The commit e9da6e9 "ARM: dma-mapping: remove custom consistent dma
> region" breaks the compatibility with existing drivers. This causes
> the following kernel oops(*1). That driver has called dma_pool_alloc()
> to allocate memory from the interrupt context, and it hits
> BUG_ON(in_interrpt()) in "get_vm_area_caller()". This patch seris
> fixes this problem with making use of the pre-allocate atomic memory
> pool which DMA is using in the same way as DMA does now.
>
> Any comment would be really appreciated.
Looks fine now. I will do some tests and apply them to my fixes-for-3.6
branch. Thanks for Your contribution!
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
WARNING: multiple messages have this Message-ID (diff)
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Hiroshi Doyu <hdoyu@nvidia.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@samsung.com,
arnd@arndb.de, linux@arm.linux.org.uk, chunsang.jeong@linaro.org,
vdumpa@nvidia.com, subashrp@gmail.com, minchan@kernel.org,
pullip.cho@samsung.com, konrad.wilk@oracle.com,
linux-tegra@vger.kernel.org
Subject: Re: [v4 0/4] ARM: dma-mapping: IOMMU atomic allocation
Date: Tue, 28 Aug 2012 18:51:00 +0200 [thread overview]
Message-ID: <503CF6F4.7060702@samsung.com> (raw)
In-Reply-To: <1346130784-23571-1-git-send-email-hdoyu@nvidia.com>
Hello,
On 8/28/2012 7:13 AM, Hiroshi Doyu wrote:
> The commit e9da6e9 "ARM: dma-mapping: remove custom consistent dma
> region" breaks the compatibility with existing drivers. This causes
> the following kernel oops(*1). That driver has called dma_pool_alloc()
> to allocate memory from the interrupt context, and it hits
> BUG_ON(in_interrpt()) in "get_vm_area_caller()". This patch seris
> fixes this problem with making use of the pre-allocate atomic memory
> pool which DMA is using in the same way as DMA does now.
>
> Any comment would be really appreciated.
Looks fine now. I will do some tests and apply them to my fixes-for-3.6
branch. Thanks for Your contribution!
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Hiroshi Doyu <hdoyu@nvidia.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@samsung.com,
arnd@arndb.de, linux@arm.linux.org.uk, chunsang.jeong@linaro.org,
vdumpa@nvidia.com, subashrp@gmail.com, minchan@kernel.org,
pullip.cho@samsung.com, konrad.wilk@oracle.com,
linux-tegra@vger.kernel.org
Subject: Re: [v4 0/4] ARM: dma-mapping: IOMMU atomic allocation
Date: Tue, 28 Aug 2012 18:51:00 +0200 [thread overview]
Message-ID: <503CF6F4.7060702@samsung.com> (raw)
In-Reply-To: <1346130784-23571-1-git-send-email-hdoyu@nvidia.com>
Hello,
On 8/28/2012 7:13 AM, Hiroshi Doyu wrote:
> The commit e9da6e9 "ARM: dma-mapping: remove custom consistent dma
> region" breaks the compatibility with existing drivers. This causes
> the following kernel oops(*1). That driver has called dma_pool_alloc()
> to allocate memory from the interrupt context, and it hits
> BUG_ON(in_interrpt()) in "get_vm_area_caller()". This patch seris
> fixes this problem with making use of the pre-allocate atomic memory
> pool which DMA is using in the same way as DMA does now.
>
> Any comment would be really appreciated.
Looks fine now. I will do some tests and apply them to my fixes-for-3.6
branch. Thanks for Your contribution!
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
next prev parent reply other threads:[~2012-08-28 16:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 5:13 [v4 0/4] ARM: dma-mapping: IOMMU atomic allocation Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` [v4 1/4] ARM: dma-mapping: atomic_pool with struct page **pages Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` [v4 2/4] ARM: dma-mapping: Refactor out to introduce __in_atomic_pool Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
[not found] ` <1346130784-23571-1-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-28 5:13 ` [v4 3/4] ARM: dma-mapping: Introduce __atomic_get_pages() for __iommu_get_pages() Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 16:51 ` Marek Szyprowski [this message]
2012-08-28 16:51 ` [v4 0/4] ARM: dma-mapping: IOMMU atomic allocation Marek Szyprowski
2012-08-28 16:51 ` Marek Szyprowski
2012-08-28 16:51 ` Marek Szyprowski
2012-08-28 5:13 ` [v4 4/4] ARM: dma-mapping: IOMMU allocates pages from atomic_pool with GFP_ATOMIC Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
2012-08-28 5:13 ` Hiroshi Doyu
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=503CF6F4.7060702@samsung.com \
--to=m.szyprowski-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=chunsang.jeong-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linaro-mm-sig-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=minchan-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=pullip.cho-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=subashrp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=vdumpa-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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.