From: "Andrianov, Vitaly" <vitalya@ti.com>
To: Michal Nazarewicz <mina86@mina86.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"kyungmin.park@samsung.com" <kyungmin.park@samsung.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-keystone@list.ti.com - Linux developers for Keystone
family of devices (May contain non-TIers)"
<linux-keystone@list.ti.com>, "Chemparathy, Cyril" <cyril@ti.com>
Subject: RE: [linux-keystone] [PATCH v2] drivers: cma: fix addressing on PAE machines
Date: Tue, 4 Dec 2012 21:03:11 +0000 [thread overview]
Message-ID: <C279DA448D408F43B343F09155C1EE9B0C228FC7@DFLE09.ent.ti.com> (raw)
In-Reply-To: <xa1tsj7l3agx.fsf@mina86.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2589 bytes --]
> -----Original Message-----
> From: Michal Nazarewicz [mailto:mpn@google.com] On Behalf Of Michal
> Nazarewicz
> Sent: Tuesday, December 04, 2012 2:05 PM
> To: Andrianov, Vitaly; Shilimkar, Santosh
> Cc: m.szyprowski@samsung.com; kyungmin.park@samsung.com; arnd@arndb.de;
> linux-kernel@vger.kernel.org; linux-keystone@list.ti.com - Linux
> developers for Keystone family of devices (May contain non-TIers);
> Chemparathy, Cyril
> Subject: Re: [linux-keystone] [PATCH v2] drivers: cma: fix addressing
> on PAE machines
>
> > On Tuesday 04 December 2012 06:37 PM, Michal Nazarewicz wrote:
> >> They are all related to the very same issue, and what the whole
> patch
> >> does is change the type used to store physical addresses from
> >> unsigned long to phys_addr_t. This is really a single change.
>
> On Tue, Dec 04 2012, Santosh Shilimkar wrote:
> > Thanks for clarification. 64 bit alignment fix and the allocation
> > range checks can be two separate fixes and that is exactly what
> change
> > log describes. You have a last say though :-) No problem if you want
> > to commit the patch as is.
>
> I don't have strong feelings on this one, but I feel like it's really a
> single change which manifests itself in a few ways. If this is
> confusing, maybe commit message could be improved, to something like:
>
> ------------- >8 ------------------------------------------------------
> -
> drivers: cma: represent physicall addresses as phys_addr_t
>
> This commit changes the CMA early initialisation code to use
> phys_addr_t for representing physical addresses instead of unsigned
> long.
>
> Without this change, among other things, dma_declare_contiguous()
> simply discards any memory regions whose address is not represtible as
> unsigned long.
>
> This is a problem on 32-bit PAE machines where unsigned long is 32-bit
> but physical address space is larger.
> ------------- 8< ------------------------------------------------------
> -
>
> Vitaly, if you could resend with that description, it would be awesome,
> and sorry for so much trouble in what appears to be a trivial patch. :P
>
Sure, I'll do that.
> --
> Best regards, _ _
> .o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
> ..o | Computer Science, MichaÅ âmina86â Nazarewicz (o o)
> ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
Regards,
Vitaly
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2012-12-04 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 15:46 Vitaly Andrianov
2012-12-03 18:19 ` Michal Nazarewicz
2012-12-04 6:46 ` [linux-keystone] " Santosh Shilimkar
2012-12-04 13:07 ` Michal Nazarewicz
2012-12-04 15:00 ` Santosh Shilimkar
2012-12-04 19:04 ` Michal Nazarewicz
2012-12-04 21:03 ` Andrianov, Vitaly [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=C279DA448D408F43B343F09155C1EE9B0C228FC7@DFLE09.ent.ti.com \
--to=vitalya@ti.com \
--cc=arnd@arndb.de \
--cc=cyril@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-keystone@list.ti.com \
--cc=m.szyprowski@samsung.com \
--cc=mina86@mina86.com \
--cc=santosh.shilimkar@ti.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
all inboxes | Powered by JetHome®