kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: tochansky@tochlab.net (tochansky at tochlab.net)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Difference dma_alloc_coherent() in x86_32 and x86_64
Date: Fri, 19 Feb 2016 18:17:59 +0300	[thread overview]
Message-ID: <dc659340425f0e31019f830792ef5eee@tochlab.net> (raw)

Hello!

I have a driver for PCI device which uses CMA framework for allocating 
big coherent blocks of memory for DMA.

Allocation looks like:

typedef struct {
     struct list_head list;
     uint32_t size8;
     void *kaddr;
     dma_addr_t paddr;
} dma_region_t;

LIST_HEAD(region_list);

......

void* AllocDMA( size_t size )
{
     dma_region_t *new_region;
     new_region = kmalloc(sizeof(dma_region_t), GFP_KERNEL);
     new_region->size8 = size;

     new_region->kaddr = dma_alloc_coherent( NULL, size, 
&new_region->paddr, GFP_KERNEL | GFP_DMA32 );

     list_add(&new_region->list, &region_list);
     printk("pcidev: cma_alloc paddr %pad kaddr %p size %d\n", 
&new_region->paddr, new_region->kaddr, new_region->size8);
     return new_region->kaddr;

}

It works fine on kernel 3.18.26 in 32bit mode.
When I reconfigure same kernel to run in 64bit mode(enabling in 
'menuconfig' option '64-bit kernel') and trying to use this driver with 
it
allocation failed with message in dmesg:
...
[ 1393.835535]  fallback device: swiotlb buffer is full (sz: 8388608 
bytes)
[ 1393.835579] pcidev: cma_alloc paddr 0xffff880234861220 kaddr          
  (null) size 8388608
...

My kernel command line is: swiotlb=16384 iommu=soft cma=256M


Anyone can explain this strange behavior?


-- 
D

                 reply	other threads:[~2016-02-19 15:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=dc659340425f0e31019f830792ef5eee@tochlab.net \
    --to=tochansky@tochlab.net \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).