All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: imirkin@alum.mit.edu, efault@gmx.de, michel@daenzer.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swiotlb: suppress warning when __GFP_NOWARN is set v2
Date: Tue, 2 Jan 2018 15:51:56 -0500	[thread overview]
Message-ID: <20180102205156.GA23475@localhost.localdomain> (raw)
In-Reply-To: <20180102121358.16215-1-christian.koenig@amd.com>

On Tue, Jan 02, 2018 at 01:13:58PM +0100, Christian König wrote:
> TTM tries to allocate coherent memory in chunks of 2MB first to improve
> TLB efficiency and falls back to allocating 4K pages if that fails.
> 
> Suppress the warning when the 2MB allocations fails since there is a
> valid fall back path.
> 
> v2: suppress warnings from swiotlb_tbl_map_single as well
> 
> Signed-off-by: Christian König <christian.koenig@amd.com>
> Reported-by: Mike Galbraith <efault@gmx.de>
> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=104082
> CC: stable@vger.kernel.org
> ---
>  lib/swiotlb.c | 44 +++++++++++++++++++++++++++++---------------
>  1 file changed, 29 insertions(+), 15 deletions(-)
> 
> diff --git a/lib/swiotlb.c b/lib/swiotlb.c
> index cea19aaf303c..ed443d65a8e2 100644
> --- a/lib/swiotlb.c
> +++ b/lib/swiotlb.c
> @@ -490,11 +490,11 @@ static void swiotlb_bounce(phys_addr_t orig_addr, phys_addr_t tlb_addr,
>  	}
>  }
>  
> -phys_addr_t swiotlb_tbl_map_single(struct device *hwdev,
> -				   dma_addr_t tbl_dma_addr,
> -				   phys_addr_t orig_addr, size_t size,
> -				   enum dma_data_direction dir,
> -				   unsigned long attrs)
> +phys_addr_t _swiotlb_tbl_map_single(struct device *hwdev,

Just ditch the '_swiotlb' and make it 'tbl_map_single'
> +				    dma_addr_t tbl_dma_addr,
> +				    phys_addr_t orig_addr, size_t size,
> +				    enum dma_data_direction dir,
> +				    unsigned long attrs, bool warn)
>  {
>  	unsigned long flags;
>  	phys_addr_t tlb_addr;
> @@ -586,7 +586,7 @@ phys_addr_t swiotlb_tbl_map_single(struct device *hwdev,
>  
>  not_found:
>  	spin_unlock_irqrestore(&io_tlb_lock, flags);
> -	if (printk_ratelimit())
> +	if (warn && printk_ratelimit())
>  		dev_warn(hwdev, "swiotlb buffer is full (sz: %zd bytes)\n", size);
>  	return SWIOTLB_MAP_ERROR;
>  found:
> @@ -605,6 +605,16 @@ phys_addr_t swiotlb_tbl_map_single(struct device *hwdev,
>  
>  	return tlb_addr;
>  }
> +
> +phys_addr_t swiotlb_tbl_map_single(struct device *hwdev,
> +				   dma_addr_t tbl_dma_addr,
> +				   phys_addr_t orig_addr, size_t size,
> +				   enum dma_data_direction dir,
> +				   unsigned long attrs)

Hm, could be my editor, but are the parameters on the same line as 'struct device *hwdev'?

> +{
> +	return _swiotlb_tbl_map_single(hwdev, tbl_dma_addr, orig_addr,
> +				       size, dir, attrs, true);
> +}
>  EXPORT_SYMBOL_GPL(swiotlb_tbl_map_single);
>  
>  /*
> @@ -613,7 +623,7 @@ EXPORT_SYMBOL_GPL(swiotlb_tbl_map_single);
>  
>  static phys_addr_t
>  map_single(struct device *hwdev, phys_addr_t phys, size_t size,
> -	   enum dma_data_direction dir, unsigned long attrs)
> +	   enum dma_data_direction dir, unsigned long attrs, bool warn)
>  {
>  	dma_addr_t start_dma_addr;
>  
> @@ -624,8 +634,8 @@ map_single(struct device *hwdev, phys_addr_t phys, size_t size,
>  	}
>  
>  	start_dma_addr = swiotlb_phys_to_dma(hwdev, io_tlb_start);
> -	return swiotlb_tbl_map_single(hwdev, start_dma_addr, phys, size,
> -				      dir, attrs);
> +	return _swiotlb_tbl_map_single(hwdev, start_dma_addr, phys, size,
> +				       dir, attrs, warn);
>  }
>  
>  /*
> @@ -713,6 +723,7 @@ void *
>  swiotlb_alloc_coherent(struct device *hwdev, size_t size,
>  		       dma_addr_t *dma_handle, gfp_t flags)
>  {
> +	bool warn = !(flags & __GFP_NOWARN);
>  	dma_addr_t dev_addr;
>  	void *ret;
>  	int order = get_order(size);
> @@ -739,7 +750,7 @@ swiotlb_alloc_coherent(struct device *hwdev, size_t size,
>  		 * will grab memory from the lowest available address range.
>  		 */
>  		phys_addr_t paddr = map_single(hwdev, 0, size,
> -					       DMA_FROM_DEVICE, 0);
> +					       DMA_FROM_DEVICE, 0, warn);
>  		if (paddr == SWIOTLB_MAP_ERROR)
>  			goto err_warn;
>  
> @@ -769,9 +780,11 @@ swiotlb_alloc_coherent(struct device *hwdev, size_t size,
>  	return ret;
>  
>  err_warn:
> -	pr_warn("swiotlb: coherent allocation failed for device %s size=%zu\n",
> -		dev_name(hwdev), size);
> -	dump_stack();
> +	if (warn) {

&& printk_ratelimit() ?

> +		pr_warn("swiotlb: coherent allocation failed for device %s size=%zu\n",
> +			dev_name(hwdev), size);
> +		dump_stack();
> +	}
>  
>  	return NULL;
>  }
> @@ -851,7 +864,7 @@ dma_addr_t swiotlb_map_page(struct device *dev, struct page *page,
>  	trace_swiotlb_bounced(dev, dev_addr, size, swiotlb_force);
>  
>  	/* Oh well, have to allocate and map a bounce buffer. */
> -	map = map_single(dev, phys, size, dir, attrs);
> +	map = map_single(dev, phys, size, dir, attrs, true);
>  	if (map == SWIOTLB_MAP_ERROR) {
>  		swiotlb_full(dev, size, dir, 1);
>  		return swiotlb_phys_to_dma(dev, io_tlb_overflow_buffer);
> @@ -989,7 +1002,8 @@ swiotlb_map_sg_attrs(struct device *hwdev, struct scatterlist *sgl, int nelems,
>  		if (swiotlb_force == SWIOTLB_FORCE ||
>  		    !dma_capable(hwdev, dev_addr, sg->length)) {
>  			phys_addr_t map = map_single(hwdev, sg_phys(sg),
> -						     sg->length, dir, attrs);
> +						     sg->length, dir, attrs,
> +						     true);

s/true/true /*Always warn.*/

>  			if (map == SWIOTLB_MAP_ERROR) {
>  				/* Don't panic here, we expect map_sg users
>  				   to do proper error handling. */
> -- 
> 2.11.0
> 

  parent reply	other threads:[~2018-01-02 20:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 12:13 [PATCH] swiotlb: suppress warning when __GFP_NOWARN is set v2 Christian König
2018-01-02 14:04 ` Mike Galbraith
2018-01-02 15:39 ` Chris Wilson
2018-01-02 16:14   ` Christian König
2018-01-02 20:51 ` Konrad Rzeszutek Wilk [this message]
2018-01-03 10:09   ` Christian König
2018-01-04 17:42 ` [RFC PATCH] swiotlb: _swiotlb_tbl_map_single() can be static kbuild test robot
2018-01-04 17:42 ` [PATCH] swiotlb: suppress warning when __GFP_NOWARN is set v2 kbuild test robot

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=20180102205156.GA23475@localhost.localdomain \
    --to=konrad.wilk@oracle.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=efault@gmx.de \
    --cc=imirkin@alum.mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel@daenzer.net \
    /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.