All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.sricharan@ti.com (R Sricharan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5] ARM: LPAE: Fix mapping in alloc_init_section for unaligned addresses
Date: Mon, 11 Feb 2013 14:39:49 +0530	[thread overview]
Message-ID: <5118B55D.1000301@ti.com> (raw)
In-Reply-To: <51151064.6050400@ti.com>

On Friday 08 February 2013 08:19 PM, Santosh Shilimkar wrote:
> On Friday 08 February 2013 08:13 PM, Christoffer Dall wrote:
>> On Fri, Feb 8, 2013 at 6:30 AM, R Sricharan <r.sricharan@ti.com> wrote:
>>> With LPAE enabled, alloc_init_section() does not map the entire
>>> address space for unaligned addresses.
>>>
>>> The issue also reproduced with CMA + LPAE. CMA tries to map 16MB
>>> with page granularity mappings during boot. alloc_init_pte()
>>> is called and out of 16MB, only 2MB gets mapped and rest remains
>>> unaccessible.
>>>
>>> Because of this OMAP5 boot is broken with CMA + LPAE enabled.
>>> Fix the issue by ensuring that the entire addresses are
>>> mapped.
>>>
>>> Signed-off-by: R Sricharan <r.sricharan@ti.com>
>>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>>> Cc: Christoffer Dall <chris@cloudcar.com>
>>> Cc: Russell King <linux@arm.linux.org.uk>
>>> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>> Tested-by: Christoffer Dall <chris@cloudcar.com>
>>
>> I don't think that I've tested this version of the patch, but ok.
>>
> Indeed. Neither I have acke'd the updated version ;)
> Tags from old patch doesn't apply anymore when patch
> is completely revamped.
>
  Ok, corrected this in the updated version.

Regards,
  Sricharan

  reply	other threads:[~2013-02-11  9:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 11:30 [PATCH V5] ARM: LPAE: Fix mapping in alloc_init_section for unaligned addresses R Sricharan
2013-02-08 14:43 ` Christoffer Dall
2013-02-08 14:49   ` Santosh Shilimkar
2013-02-11  9:09     ` R Sricharan [this message]
2013-02-11  9:10   ` R Sricharan
2013-02-08 15:21 ` Catalin Marinas

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=5118B55D.1000301@ti.com \
    --to=r.sricharan@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.