From: "Breton M. Saunders" <breton.saunders@ntlworld.com>
To: alsa-devel@lists.sourceforge.net
Subject: Memory allocation problem using GFP_COMP?
Date: Fri, 12 Jan 2007 17:37:05 +0000 [thread overview]
Message-ID: <45A7C741.6060904@ntlworld.com> (raw)
Folks,
I've got a problem in allocating DMA memory on ARM for a driver on 2.6.19:
The function snd_malloc_dev_pages requests memory using the
dma_alloc_coherent function on line 222 of sound/core/memalloc.c. This
allocation is done with the bit __GFP_COMP set, which throws an oops in
the ARM memory allocation __dma_alloc. My understanding from speaking
with Russell King is that __GFP_COMP should never be specified when
calling dma_alloc_coherent.
Is this a bug?
Cheers,
-Brett
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2007-01-12 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 17:37 Breton M. Saunders [this message]
2007-01-12 18:10 ` Memory allocation problem using GFP_COMP? Takashi Iwai
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=45A7C741.6060904@ntlworld.com \
--to=breton.saunders@ntlworld.com \
--cc=alsa-devel@lists.sourceforge.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.