public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joerg.roedel@amd.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
	tony.luck@intel.com, linux-ia64@vger.kernel.org,
	iommu@lists.linux-foundation.org
Subject: Re: [PATCH 5/5] swiotlb: remove GFP_DMA hack in swiotlb_alloc_coherent
Date: Mon, 8 Sep 2008 14:02:18 +0200	[thread overview]
Message-ID: <20080908120218.GM3189@amd.com> (raw)
In-Reply-To: <1220865014-1169-6-git-send-email-fujita.tomonori@lab.ntt.co.jp>

On Mon, Sep 08, 2008 at 06:10:14PM +0900, FUJITA Tomonori wrote:
> The callers are supposed to set up the gfp flags appropriately.
> 
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>

Acked-by: Joerg Roedel <joerg.roedel@amd.com>

> ---
>  lib/swiotlb.c |    7 -------
>  1 files changed, 0 insertions(+), 7 deletions(-)
> 
> diff --git a/lib/swiotlb.c b/lib/swiotlb.c
> index 977edbd..3066ffe 100644
> --- a/lib/swiotlb.c
> +++ b/lib/swiotlb.c
> @@ -467,13 +467,6 @@ swiotlb_alloc_coherent(struct device *hwdev, size_t size,
>  	void *ret;
>  	int order = get_order(size);
>  
> -	/*
> -	 * XXX fix me: the DMA API should pass us an explicit DMA mask
> -	 * instead, or use ZONE_DMA32 (ia64 overloads ZONE_DMA to be a ~32
> -	 * bit range instead of a 16MB one).
> -	 */
> -	flags |= GFP_DMA;
> -
>  	ret = (void *)__get_free_pages(flags, order);
>  	if (ret && address_needs_mapping(hwdev, virt_to_bus(ret))) {
>  		/*
> -- 
> 1.5.5.GIT
> 
> 

-- 
           |           AMD Saxony Limited Liability Company & Co. KG
 Operating |         Wilschdorfer Landstr. 101, 01109 Dresden, Germany
 System    |                  Register Court Dresden: HRA 4896
 Research  |              General Partner authorized to represent:
 Center    |             AMD Saxony LLC (Wilmington, Delaware, US)
           | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy


  reply	other threads:[~2008-09-08 12:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08  9:10 [PATCH 0/5] fix exhaustion of ZONE_DMA with swiotlb (in x86 tree) FUJITA Tomonori
2008-09-08  9:10 ` [PATCH 1/5] ia64: dma_alloc_coherent always use GFP_DMA FUJITA Tomonori
2008-09-08  9:10   ` [PATCH 2/5] x86: move pci-nommu's dma_mask check to common code FUJITA Tomonori
2008-09-08  9:10     ` [PATCH 3/5] x86: fix nommu_alloc_coherent allocation with NULL device argument FUJITA Tomonori
2008-09-08  9:10       ` [PATCH 4/5] x86: dma_alloc_coherent sets gfp flags properly FUJITA Tomonori
2008-09-08  9:10         ` [PATCH 5/5] swiotlb: remove GFP_DMA hack in swiotlb_alloc_coherent FUJITA Tomonori
2008-09-08 12:02           ` Joerg Roedel [this message]
2008-09-08 12:01         ` [PATCH 4/5] x86: dma_alloc_coherent sets gfp flags properly Joerg Roedel
2008-09-08 12:01       ` [PATCH 3/5] x86: fix nommu_alloc_coherent allocation with NULL device argument Joerg Roedel
2008-09-08 12:01     ` [PATCH 2/5] x86: move pci-nommu's dma_mask check to common code Joerg Roedel
2008-09-08 12:00 ` [PATCH 0/5] fix exhaustion of ZONE_DMA with swiotlb (in x86 tree) Joerg Roedel
2008-09-08 13:52   ` Ingo Molnar
2008-09-09 10:41 ` KAMEZAWA Hiroyuki

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=20080908120218.GM3189@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tony.luck@intel.com \
    /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