From: Christoph Hellwig <hch@lst.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org, Michal Simek <monstr@monstr.eu>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
linux-alpha@vger.kernel.org, linux-snps-arc@lists.infradead.org,
linux-c6x-dev@linux-c6x.org, linux-m68k@lists.linux-m68k.org,
openrisc@lists.librecores.org, linux-parisc@vger.kernel.org,
linux-s390@vger.kernel.org, sparclinux@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 19:35:09 +0100 [thread overview]
Message-ID: <20181214183509.GA5247@lst.de> (raw)
In-Reply-To: <20181214181056.GA17941@ravnborg.org>
On Fri, Dec 14, 2018 at 07:10:56PM +0100, Sam Ravnborg wrote:
> Hi Christoph,
>
> I stumbled upon this one:
>
> #define __get_dma_pages(gfp_mask, order) \
> __get_free_pages((gfp_mask) | GFP_DMA, (order))
This isn't directly related to the dma mapping, but another place
that hides GFP_DMA allocations. So no need for the treatment,
but we really should kill this obsfucating wrapper..
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org, Michal Simek <monstr@monstr.eu>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
linux-alpha@vger.kernel.org, linux-snps-arc@lists.infradead.org,
linux-c6x-dev@linux-c6x.org, linux-m68k@lists.linux-m68k.org,
openrisc@lists.librecores.org, linux-parisc@vger.kernel.org,
linux-s390@vger.kernel.org, sparclinux@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 18:35:09 +0000 [thread overview]
Message-ID: <20181214183509.GA5247@lst.de> (raw)
In-Reply-To: <20181214181056.GA17941@ravnborg.org>
On Fri, Dec 14, 2018 at 07:10:56PM +0100, Sam Ravnborg wrote:
> Hi Christoph,
>
> I stumbled upon this one:
>
> #define __get_dma_pages(gfp_mask, order) \
> __get_free_pages((gfp_mask) | GFP_DMA, (order))
This isn't directly related to the dma mapping, but another place
that hides GFP_DMA allocations. So no need for the treatment,
but we really should kill this obsfucating wrapper..
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 19:35:09 +0100 [thread overview]
Message-ID: <20181214183509.GA5247@lst.de> (raw)
In-Reply-To: <20181214181056.GA17941@ravnborg.org>
On Fri, Dec 14, 2018@07:10:56PM +0100, Sam Ravnborg wrote:
> Hi Christoph,
>
> I stumbled upon this one:
>
> #define __get_dma_pages(gfp_mask, order) \
> __get_free_pages((gfp_mask) | GFP_DMA, (order))
This isn't directly related to the dma mapping, but another place
that hides GFP_DMA allocations. So no need for the treatment,
but we really should kill this obsfucating wrapper..
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 19:35:09 +0100 [thread overview]
Message-ID: <20181214183509.GA5247@lst.de> (raw)
In-Reply-To: <20181214181056.GA17941@ravnborg.org>
On Fri, Dec 14, 2018 at 07:10:56PM +0100, Sam Ravnborg wrote:
> Hi Christoph,
>
> I stumbled upon this one:
>
> #define __get_dma_pages(gfp_mask, order) \
> __get_free_pages((gfp_mask) | GFP_DMA, (order))
This isn't directly related to the dma mapping, but another place
that hides GFP_DMA allocations. So no need for the treatment,
but we really should kill this obsfucating wrapper..
next prev parent reply other threads:[~2018-12-14 18:35 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 8:25 ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14 8:25 ` [OpenRISC] " Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_* Christoph Hellwig
2018-12-14 8:25 ` [OpenRISC] " Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 9:54 ` Geert Uytterhoeven
2018-12-14 9:54 ` [OpenRISC] " Geert Uytterhoeven
2018-12-14 9:54 ` Geert Uytterhoeven
2018-12-14 9:54 ` Geert Uytterhoeven
2018-12-14 9:54 ` Geert Uytterhoeven
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 9:55 ` [OpenRISC] " Geert Uytterhoeven
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 11:47 ` [OpenRISC] " Christoph Hellwig
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 12:36 ` Geert Uytterhoeven
2018-12-14 12:36 ` [OpenRISC] " Geert Uytterhoeven
2018-12-14 12:36 ` Geert Uytterhoeven
2018-12-14 12:36 ` Geert Uytterhoeven
2018-12-14 14:14 ` Greg Ungerer
2018-12-14 14:14 ` [OpenRISC] " Greg Ungerer
2018-12-14 14:14 ` Greg Ungerer
2018-12-14 14:14 ` Greg Ungerer
2018-12-14 14:14 ` Greg Ungerer
2018-12-14 14:14 ` Greg Ungerer
2018-12-17 11:59 ` Christoph Hellwig
2018-12-17 11:59 ` [OpenRISC] " Christoph Hellwig
2018-12-17 11:59 ` Christoph Hellwig
2018-12-17 11:59 ` Christoph Hellwig
2019-01-11 6:09 ` Greg Ungerer
2018-12-14 12:12 ` Eugeniy Paltsev
2018-12-14 12:12 ` [OpenRISC] " Eugeniy Paltsev
2018-12-14 12:12 ` Eugeniy Paltsev
2018-12-14 12:12 ` Eugeniy Paltsev
2018-12-14 12:12 ` Eugeniy Paltsev
2018-12-14 12:21 ` hch
2018-12-14 12:21 ` [OpenRISC] " hch
2018-12-14 12:21 ` hch-jcswGhMUV9g
2018-12-14 12:21 ` hch
2018-12-14 12:21 ` hch
2018-12-14 18:10 ` Sam Ravnborg
2018-12-14 18:10 ` [OpenRISC] " Sam Ravnborg
2018-12-14 18:10 ` Sam Ravnborg
2018-12-14 18:10 ` Sam Ravnborg
2018-12-14 18:35 ` Christoph Hellwig [this message]
2018-12-14 18:35 ` [OpenRISC] " Christoph Hellwig
2018-12-14 18:35 ` Christoph Hellwig
2018-12-14 18:35 ` Christoph Hellwig
2018-12-14 8:25 ` [PATCH 2/2] dma-mapping: deprecate dma_zalloc_coherent Christoph Hellwig
2018-12-14 8:25 ` [OpenRISC] " Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 13:33 ` ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14 13:33 ` [OpenRISC] " Christoph Hellwig
2018-12-14 13:33 ` Christoph Hellwig
2018-12-14 13:33 ` Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-19 16:59 ` [OpenRISC] " Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:34 ` hch
2018-12-20 14:34 ` [OpenRISC] " hch
2018-12-20 14:34 ` hch
2018-12-20 14:34 ` hch
2018-12-20 14:34 ` hch
2018-12-20 14:39 ` Eugeniy Paltsev
2018-12-20 14:39 ` Eugeniy Paltsev
2018-12-20 14:39 ` Eugeniy Paltsev
2018-12-20 14:39 ` Eugeniy Paltsev
2018-12-20 14:46 ` hch
2018-12-20 14:46 ` [OpenRISC] " hch
2018-12-20 14:46 ` hch
2018-12-20 14:46 ` hch
2018-12-20 14:46 ` hch
2018-12-20 17:37 ` hch
2018-12-20 17:37 ` [OpenRISC] " hch
2018-12-20 17:37 ` hch
2018-12-20 17:37 ` hch
2018-12-20 17:37 ` hch
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=20181214183509.GA5247@lst.de \
--to=hch@lst.de \
--cc=ashutosh.dixit@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=monstr@monstr.eu \
--cc=openrisc@lists.librecores.org \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.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.