linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Remi Machet <rmachet@slac.stanford.edu>
Cc: Linux PPC <linuxppc-dev@ozlabs.org>
Subject: Re: Hard-coded virtual address used by dma_alloc_coherent
Date: Thu, 24 Jul 2008 14:29:12 -0500	[thread overview]
Message-ID: <4888D808.8000406@freescale.com> (raw)
In-Reply-To: <1216927153.19203.62.camel@pcds-ts102.slac.stanford.edu>

Remi Machet wrote:
> I have noticed that the DMA allocation for non-coherent PowerPC
> architecture is using a hard coded virtual memory address for its memory
> pool. This address is typically 0xFF100000 (set by
> CONFIG_CONSISTENT_START) and can conflict with early ioremap in systems
> that enable HIGHMEM.
> 
> Is there any reason why we have to use an arbitrary virtual address ? If
> the virtual address must be known at compile time, can't we use fixmap ?

The hardcoded address predates when fixmap was added to powerpc.  It 
should be updated to use fixmap.

> I also can't figure out why we need to use a virtual address known at
> compilation time and cannot just allocate pages using get_free_pages and
> mark them as non cacheable and non swappable.

We probably don't need a compile-time address, though we can't just 
change the page attributes in-place as the pages will often covered by 
large TLB entries.

-Scott

  reply	other threads:[~2008-07-24 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 19:19 Hard-coded virtual address used by dma_alloc_coherent Remi Machet
2008-07-24 19:29 ` Scott Wood [this message]
2008-07-24 21:43   ` Remi Machet

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=4888D808.8000406@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rmachet@slac.stanford.edu \
    /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).