mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shanker Donthineni <shankerd@codeaurora.org>
To: Robert Richter <rrichter@cavium.com>,
	Marc Zyngier <marc.zyngier@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 8/8] irqchip, gicv3-its, cma: Use CMA for allocation of large device tables
Date: Tue, 14 Mar 2017 12:40:45 -0500	[thread overview]
Message-ID: <3c462655-fb2c-ede7-1dc0-ca5c7f64904f@codeaurora.org> (raw)
In-Reply-To: <20170306125739.19445-9-rrichter@cavium.com>

Hi Robert,

I don't see anywhere in this patch, code calls explicitly CMA API to allocate memory for device table.  The CMA feature is an optional in kernel, and will be handled transparently inside the the DMA layer. It would be nicer to not mention CMA word in the commit subject.


On 03/06/2017 06:57 AM, Robert Richter wrote:
> The gicv3-its device table may have a size of up to 16MB. With 4k
> pagesize the maximum size of memory allocation is 4MB. Use CMA for
> allocation of large tables.
Just say use devm_alloc_coherent() to allocate memory.

> We use the device managed version of dma_alloc_coherent(). Thus, we
> don't need to release it manually on device removal.
>
> Signed-off-by: Robert Richter <rrichter@cavium.com>
> ---
>  drivers/irqchip/irq-gic-v3-its.c | 69 +++++++++++++++++++++++-----------------
>  1 file changed, 40 insertions(+), 29 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
> index 6625b3a505f0..6d293a0165b0 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -21,6 +21,7 @@
>  #include <linux/delay.h>
>  #include <linux/device.h>
>  #include <linux/dma-iommu.h>
> +#include <linux/dma-mapping.h>
>  #include <linux/interrupt.h>
>  #include <linux/irqdomain.h>
>  #include <linux/acpi_iort.h>
> @@ -864,6 +865,7 @@ static int its_setup_baser(struct its_node *its, struct its_baser *baser,
>  	u64 type = GITS_BASER_TYPE(val);
>  	u32 alloc_pages;
>  	void *base;
> +	dma_addr_t dma_handle;
>  	u64 tmp;
>  
>  retry_alloc_baser:
> @@ -876,13 +878,26 @@ static int its_setup_baser(struct its_node *its, struct its_baser *baser,
>  		order = get_order(GITS_BASER_PAGES_MAX * psz);
>  	}
>  
> -	base = (void *)devm_get_free_pages(&its->dev, GFP_KERNEL | __GFP_ZERO,
> -					   order);
> -	if (!base)
> +	base = dmam_alloc_coherent(&its->dev,
> +				PAGE_ORDER_TO_SIZE(order),
> +				&dma_handle,
> +				GFP_KERNEL | __GFP_ZERO);
Not just for 1st level device table, you have do a similar code change when allocating memory for 2nd level device table.
> +
> +	if (!base && order >= MAX_ORDER) {
> +		order = MAX_ORDER - 1;
> +		dev_warn(&its->dev, "Device Table too large, reduce ids %u->%u, no CMA memory available\n",
> +			its->device_ids,
> +			ilog2(PAGE_ORDER_TO_SIZE(order) / (int)esz));
> +		goto retry_alloc_baser;
> +	}
> +
> +	if (!base) {
> +		dev_err(&its->dev, "Failed to allocate device table\n");
>  		return -ENOMEM;
> +	}
>  
>  retry_baser:
> -	val = (virt_to_phys(base)				 |
> +	val = (dma_handle					 |
>  		(type << GITS_BASER_TYPE_SHIFT)			 |
>  		((esz - 1) << GITS_BASER_ENTRY_SIZE_SHIFT)	 |
>  		((alloc_pages - 1) << GITS_BASER_PAGES_SHIFT)	 |
> @@ -923,29 +938,28 @@ static int its_setup_baser(struct its_node *its, struct its_baser *baser,
>  		goto retry_baser;
>  	}
>  
> -	if ((val ^ tmp) & GITS_BASER_PAGE_SIZE_MASK) {
> -		/*
> -		 * Page size didn't stick. Let's try a smaller
> -		 * size and retry. If we reach 4K, then
> -		 * something is horribly wrong...
> -		 */
> -		devm_free_pages(&its->dev, (unsigned long)base);
> -		baser->base = NULL;
> -
> -		switch (psz) {
> -		case SZ_16K:
> -			psz = SZ_4K;
> -			goto retry_alloc_baser;
> -		case SZ_64K:
> -			psz = SZ_16K;
> -			goto retry_alloc_baser;
> +	if (val != tmp) {
> +		dmam_free_coherent(&its->dev, PAGE_ORDER_TO_SIZE(order),
> +				base, dma_handle);
> +
> +		if ((val ^ tmp) & GITS_BASER_PAGE_SIZE_MASK) {
> +			/*
> +			 * Page size didn't stick. Let's try a smaller
> +			 * size and retry. If we reach 4K, then
> +			 * something is horribly wrong...
> +			 */
> +			switch (psz) {
> +			case SZ_16K:
> +				psz = SZ_4K;
> +				goto retry_alloc_baser;
> +			case SZ_64K:
> +				psz = SZ_16K;
> +				goto retry_alloc_baser;
> +			}
>  		}
> -	}
>  
> -	if (val != tmp) {
>  		dev_err(&its->dev, "%s doesn't stick: %llx %llx\n",
>  		       its_base_type_string[type], val, tmp);
> -		devm_free_pages(&its->dev, (unsigned long)base);
>  		return -ENXIO;
>  	}
>  
> @@ -1003,12 +1017,6 @@ static bool its_parse_baser_device(struct its_node *its, struct its_baser *baser
>  	 * feature is not supported by hardware.
>  	 */
>  	new_order = max_t(u32, get_order(esz << ids), new_order);
> -	if (new_order >= MAX_ORDER) {
> -		new_order = MAX_ORDER - 1;
> -		ids = ilog2(PAGE_ORDER_TO_SIZE(new_order) / (int)esz);
> -		dev_warn(&its->dev, "Device Table too large, reduce ids %u->%u\n",
> -			its->device_ids, ids);
> -	}
>  
>  	*order = new_order;
>  
> @@ -1698,6 +1706,9 @@ static int __init its_init_one(struct its_node *its)
>  		return err;
>  	}
>  
> +	/* Setup dma_ops for dmam_alloc_coherent() */
> +	arch_setup_dma_ops(&its->dev, 0, 0, NULL, true);
> +
Why you are hard-coding DMA coherent property to true here ? It breaks the MSI(x) functionally on systems where ITS hardware doesn't support coherency.
>  	its_base = devm_ioremap(&its->dev, its->phys_base, its->phys_size);
>  	if (!its_base) {
>  		dev_warn(&its->dev, "Unable to map ITS registers\n");

-- 
Shanker Donthineni
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2017-03-14 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 12:57 [PATCH v2 0/8] irqchip/gic-v3-its: Implement ITS nodes as kernel devices and use CMA Robert Richter
2017-03-06 12:57 ` [PATCH v2 1/8] irqchip/gic-v3-its: Initialize its nodes in probe order Robert Richter
2017-03-06 12:57 ` [PATCH v2 2/8] irqchip/gic-v3-its: Initialize MSIs with subsys_initcalls Robert Richter
2017-03-06 12:57 ` [PATCH v2 3/8] irqchip/gic-v3-its: Split probing from its node initialization Robert Richter
2017-03-06 12:57 ` [PATCH v2 4/8] irqchip/gic-v3-its: Decouple its initialization from gic Robert Richter
2017-03-06 12:57 ` [PATCH v2 5/8] irqchip/gic-v3-its: Prevent its init ordering dependencies Robert Richter
2017-03-06 12:57 ` [PATCH v2 6/8] irqchip/gic-v3-its: Initialize its nodes later Robert Richter
2017-03-06 12:57 ` [PATCH v2 7/8] irqchip/gic-v3-its: Handle its nodes as kernel devices Robert Richter
2017-03-06 12:57 ` [PATCH v2 8/8] irqchip, gicv3-its, cma: Use CMA for allocation of large device tables Robert Richter
2017-03-14 17:40   ` Shanker Donthineni [this message]
2017-03-15 18:37     ` Robert Richter
2017-03-15 18:46       ` Marc Zyngier
2017-03-16 13:31         ` Robert Richter
2017-03-16 13:41           ` Marc Zyngier
2017-03-16 14:03             ` Shanker Donthineni

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=3c462655-fb2c-ede7-1dc0-ca5c7f64904f@codeaurora.org \
    --to=shankerd@codeaurora.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=rrichter@cavium.com \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome