linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Earl Olsen <earl.olsen@dilithiumnetworks.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: problems with dma_alloc_coherent and consistent_alloc
Date: Wed, 5 Oct 2005 20:05:32 -0300	[thread overview]
Message-ID: <20051005230532.GA10220@logos.cnet> (raw)
In-Reply-To: <B8561865DB141248943E2376D0E8521501420346@DHOST001-17.DEX001.intermedia.net>

On Wed, Oct 05, 2005 at 02:21:01PM -0700, Earl Olsen wrote:
> 
> (Sorry, I had trouble outlook and messed up the subject line)
> 
> We are using a PPC 750 with 512m of RAM.

I dont know much about your hardware, but I'll shoot anyway.

> 1) When we try to allocate memory using consistent_alloc we get a 
> failure with get_pteptr - there is no pte.  
> 
> 2) When we try using dma_alloc_coherent the system locks up when
> we try to access that memory.
> 
> I'm guessing these problems stem from the memory being allocated
> is from the 384 bytes of RAM that gets handed over to BATs 2 AND 3,

You mean Mbytes?

> not the remaining memory handled by the page table.
> 
> In the first case, pages are allocated, but since if came from the
> BAT region, will not have a page table mapping.
> 
> In the second case, if dma_alloc_init gets memory from the BAT
> region, then we have the BAT and page management mechanisms
> both trying to control the memory.
> 
> Does this sound like a good theory?  Has anybody encountered
> this problem before?

The kernel should create pte tables for all RAM, even if parts of 
memory are not accessed through pagetable mappings.

      reply	other threads:[~2005-10-06 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 21:21 problems with dma_alloc_coherent and consistent_alloc Earl Olsen
2005-10-05 23:05 ` Marcelo Tosatti [this message]

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=20051005230532.GA10220@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=earl.olsen@dilithiumnetworks.com \
    --cc=linuxppc-embedded@ozlabs.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).