From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jeff Ohlstein <johlstei@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dwalker@codeaurora.org,
Catalin Marinas <catalin.marinas@arm.com>,
Nicolas Pitre <nico@marvell.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] arm: dma-mapping: move consistent_init to early_initcall
Date: Thu, 2 Dec 2010 22:19:09 +0000 [thread overview]
Message-ID: <20101202221909.GK29347@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1291327879-28073-1-git-send-email-johlstei@codeaurora.org>
On Thu, Dec 02, 2010 at 02:11:18PM -0800, Jeff Ohlstein wrote:
> Some machines require the use of coherent memory to bring up auxillary
> cpus, and thus want to use dma_alloc_coherent prior to smp_init
> completing.
I'd like to see the rest of the code to indicate why you need DMA
coherent memory for SMP boot. It seems to me quite unnecessary.
DMA coherent memory is meant for talking to devices, not to other
CPUs which will be part of the symmetric part of the system.
next prev parent reply other threads:[~2010-12-02 22:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 22:11 [PATCH] arm: dma-mapping: move consistent_init to early_initcall Jeff Ohlstein
2010-12-02 22:19 ` Russell King - ARM Linux [this message]
2010-12-03 20:06 ` Saravana Kannan
2010-12-03 20:36 ` Russell King - ARM Linux
2010-12-03 22:45 ` Jamie Iles
2010-12-07 6:22 ` Saravana Kannan
2010-12-09 9:23 ` skannan
2010-12-09 10:38 ` Russell King - ARM Linux
2010-12-10 0:58 ` Saravana Kannan
2010-12-10 10:00 ` Catalin Marinas
2010-12-12 4:58 ` Saravana Kannan
2010-12-13 15:26 ` Catalin Marinas
2010-12-17 2:55 ` Saravana Kannan
2010-12-17 9:48 ` Russell King - ARM Linux
2010-12-17 10:26 ` Saravana Kannan
2010-12-17 10:56 ` Russell King - ARM Linux
2010-12-17 11:09 ` Saravana Kannan
2010-12-17 11:31 ` Catalin Marinas
2010-12-17 23:14 ` Saravana Kannan
2010-12-20 23:22 ` Saravana Kannan
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=20101202221909.GK29347@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=catalin.marinas@arm.com \
--cc=dwalker@codeaurora.org \
--cc=johlstei@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@marvell.com \
--cc=tj@kernel.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).