From: Dan Williams <dan.j.williams@intel.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>, Timur Tabi <timur.tabi@gmail.com>,
Scott Wood <scottwood@freescale.com>,
Dan Malek <ppc6dev@digitaldans.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] fsldma: add support to 36-bit physical address
Date: Thu, 23 Sep 2010 15:11:57 -0700 [thread overview]
Message-ID: <AANLkTinfHQGqWx2txwG4-nORcwcFD9dYstmVv8iK9oZ8@mail.gmail.com> (raw)
In-Reply-To: <492E9153-2D3E-4DA2-AD04-4F92C94DB3A7@kernel.crashing.org>
On Tue, Sep 21, 2010 at 10:41 PM, Kumar Gala <galak@kernel.crashing.org> wr=
ote:
>
> On Sep 21, 2010, at 5:34 PM, Timur Tabi wrote:
>
>> On Tue, Sep 21, 2010 at 5:17 PM, Scott Wood <scottwood@freescale.com> wr=
ote:
>>
>>> It needs to be the actual device that is performing the DMA -- the
>>> platform may need to do things such as IOMMU manipulation where
>>> knowing the device matters.
>>
>> Ok, this all makes sense. =A0So it appears that the patch is valid, at
>> least in theory. =A0I would like to see some testing of it, but I
>> realize that may be too difficult. =A0There's no easy way to force an
>> allocation above 4GB.
>
> I think the patch is pretty safe w/o testing. =A0However I agree we need =
a better solution to testing 36-bit addressing.
I'll take that as an acked-by, but I'll wait for the next version of
the patch with the completed changelog before acting on it.
--
Dan
prev parent reply other threads:[~2010-09-23 22:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 10:57 [PATCH] fsldma: add support to 36-bit physical address Li Yang
2010-09-21 12:55 ` Kumar Gala
2010-09-21 21:24 ` Timur Tabi
2010-09-21 21:34 ` Scott Wood
2010-09-21 21:43 ` Timur Tabi
2010-09-21 21:49 ` Scott Wood
2010-09-21 22:04 ` Timur Tabi
2010-09-21 22:05 ` Dan Malek
2010-09-21 22:08 ` Timur Tabi
2010-09-21 22:17 ` Scott Wood
2010-09-21 22:34 ` Timur Tabi
2010-09-22 5:41 ` Kumar Gala
2010-09-23 22:11 ` Dan Williams [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=AANLkTinfHQGqWx2txwG4-nORcwcFD9dYstmVv8iK9oZ8@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ppc6dev@digitaldans.com \
--cc=scottwood@freescale.com \
--cc=timur.tabi@gmail.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;
as well as URLs for NNTP newsgroup(s).