From: Catalin Marinas <catalin.marinas@arm.com>
To: Anup Patel <anup.patel@linaro.org>
Cc: "msalter@redhat.com" <msalter@redhat.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>, patches <patches@apm.com>,
Loc Ho <lho@apm.com>, "ksankaran@apm.com" <ksankaran@apm.com>
Subject: Re: [PATCH] arm64: make CONFIG_ZONE_DMA user settable
Date: Fri, 18 Jul 2014 15:59:31 +0100 [thread overview]
Message-ID: <20140718145931.GD4608@arm.com> (raw)
In-Reply-To: <CALrVBkvWejppnR2+Qwc__LT2d=0bQtEwF325kMSmQ=7BeUBrdw@mail.gmail.com>
On Fri, Jul 18, 2014 at 12:58:31PM +0100, Anup Patel wrote:
> On 18 July 2014 16:37, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > From 133656f8378dbb838ad5f12ea29aa9303d7ca922 Mon Sep 17 00:00:00 2001
> > From: Catalin Marinas <catalin.marinas@arm.com>
> > Date: Fri, 18 Jul 2014 11:54:37 +0100
> > Subject: [PATCH] arm64: Create non-empty ZONE_DMA when DRAM starts above 4GB
> >
> > ZONE_DMA is created to allow 32-bit only devices to access memory in the
> > absence of an IOMMU. On systems where the memory starts above 4GB, it is
> > expected that some devices have a DMA offset hardwired to be able to
> > access the bottom of the memory. Linux currently supports DT bindings
> > for the DMA offsets but they are not (easily) available early during
> > boot.
> >
> > This patch tries to guess a DMA offset and assumes that ZONE_DMA
> > corresponds to the 32-bit mask above the start of DRAM.
> >
> > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> > Cc: Mark Salter <msalter@redhat.com>
[...]
> Linux-3.16-rcX is broken on X-Gene Mustang because
> on X-Gene Mustang the DRAM starts at 0x4000000000.
>
> I have tested your patch and the original patch from
> this thread. Both patches fixes the issue for X-Gene
> Mustang and Linux-3.16-rc5 happily boots on X-Gene.
>
> Can you to send your patch as Linux-3.16-rcX fix?
It needs some more testing and if there is time, yes, otherwise it will
just be cc stable.
> For your patch, you can have:
> Tested-by: Anup Patel <anup.patel@linaro.org>
Thanks.
--
Catalin
next prev parent reply other threads:[~2014-07-18 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 5:05 [PATCH] arm64: make CONFIG_ZONE_DMA user settable Mark Salter
2014-06-23 9:01 ` Russell King - ARM Linux
2014-06-23 11:09 ` Catalin Marinas
2014-06-23 13:17 ` Mark Salter
2014-06-24 14:14 ` Catalin Marinas
2014-06-24 14:38 ` Mark Salter
2014-07-18 11:07 ` Catalin Marinas
2014-07-18 11:58 ` Anup Patel
2014-07-18 14:59 ` Catalin Marinas [this message]
2014-07-21 21:56 ` Mark Salter
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=20140718145931.GD4608@arm.com \
--to=catalin.marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=anup.patel@linaro.org \
--cc=ksankaran@apm.com \
--cc=lho@apm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=patches@apm.com \
/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