From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Christoffer Dall <chris@cloudcar.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Tony Lindgren <tony@atomide.com>,
"Jeremy C. Andrus" <jeremya@cs.columbia.edu>,
Catalin Marinas <catalin.marinas@arm.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [RFC PATCH] ARM: mm: Fix alloc_init_section bug on LPAE
Date: Sat, 26 Jan 2013 10:20:11 +0530 [thread overview]
Message-ID: <51036083.4040407@ti.com> (raw)
In-Reply-To: <1359160318-27068-1-git-send-email-chris@cloudcar.com>
Hi Christoffer,
On Saturday 26 January 2013 06:01 AM, Christoffer Dall wrote:
> When using LPAE the call to alloc_init_pte is passed then end address
> for the entire 1st level page table region, and the code unluckily ends
> up going over the bounds of the single allocated PTE, which is sad.
>
> This caused LPAE boot on omap5 to crash.
>
> There may be some hidden mystery in the boot code that I'm unaware of
> or it may be assumed that all mappings are always mappable as sections
> on LPAE and therefore omap5 just does something bad, in which case this
> patch isn't the right fix, but I'd be happy to be told the reason.
>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Jeremy C. Andrus <jeremya@cs.columbia.edu>
> Signed-off-by: Christoffer Dall <chris@cloudcar.com>
> ---
I was about to reply on the LPAE boot issue you mentioned in other
email. We have seen couple of issues with LPAE on OMAP5 and sent the
fixes.
[1] ARM: LPAE: Fix alloc_init_section to flush all the pmd entries
[2] ARM: LPAE: Fix mapping in alloc_init_pte for unaligned addresses
Both needs ack from Catalin and RMK's ok to get into the patch system.
Can you please check if they work for you ? I expect the [1] should
make your board boot on OMAP5.
Regards
Santosh
[1] https://patchwork.kernel.org/patch/1278031/
[2] https://patchwork.kernel.org/patch/1472031/
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: mm: Fix alloc_init_section bug on LPAE
Date: Sat, 26 Jan 2013 10:20:11 +0530 [thread overview]
Message-ID: <51036083.4040407@ti.com> (raw)
In-Reply-To: <1359160318-27068-1-git-send-email-chris@cloudcar.com>
Hi Christoffer,
On Saturday 26 January 2013 06:01 AM, Christoffer Dall wrote:
> When using LPAE the call to alloc_init_pte is passed then end address
> for the entire 1st level page table region, and the code unluckily ends
> up going over the bounds of the single allocated PTE, which is sad.
>
> This caused LPAE boot on omap5 to crash.
>
> There may be some hidden mystery in the boot code that I'm unaware of
> or it may be assumed that all mappings are always mappable as sections
> on LPAE and therefore omap5 just does something bad, in which case this
> patch isn't the right fix, but I'd be happy to be told the reason.
>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Jeremy C. Andrus <jeremya@cs.columbia.edu>
> Signed-off-by: Christoffer Dall <chris@cloudcar.com>
> ---
I was about to reply on the LPAE boot issue you mentioned in other
email. We have seen couple of issues with LPAE on OMAP5 and sent the
fixes.
[1] ARM: LPAE: Fix alloc_init_section to flush all the pmd entries
[2] ARM: LPAE: Fix mapping in alloc_init_pte for unaligned addresses
Both needs ack from Catalin and RMK's ok to get into the patch system.
Can you please check if they work for you ? I expect the [1] should
make your board boot on OMAP5.
Regards
Santosh
[1] https://patchwork.kernel.org/patch/1278031/
[2] https://patchwork.kernel.org/patch/1472031/
next prev parent reply other threads:[~2013-01-26 4:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 0:31 [RFC PATCH] ARM: mm: Fix alloc_init_section bug on LPAE Christoffer Dall
2013-01-26 0:31 ` Christoffer Dall
2013-01-26 4:50 ` Santosh Shilimkar [this message]
2013-01-26 4:50 ` Santosh Shilimkar
2013-01-26 6:15 ` Christoffer Dall
2013-01-26 6:15 ` Christoffer Dall
2013-02-01 17:55 ` Catalin Marinas
2013-02-01 17:55 ` 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=51036083.4040407@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=catalin.marinas@arm.com \
--cc=chris@cloudcar.com \
--cc=jeremya@cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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 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.