From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] ARM: pxa: Fix out of vmalloc space bug
Date: Fri, 11 Jul 2014 13:00:47 +0200 [thread overview]
Message-ID: <3632586.xKfZNAEmjS@avalon> (raw)
In-Reply-To: <CAOesGMiRjcWUnwsKBwK_dwWZP1EZpSVJyf5GyPkZJzP63SbS4Q@mail.gmail.com>
Hi Olof,
On Thursday 10 July 2014 09:56:32 Olof Johansson wrote:
> On Thu, Jul 10, 2014 at 5:10 AM, Ezequiel Garcia wrote:
> > On 10 Apr 08:31 PM, Nicolas Pitre wrote:
> >> On Fri, 11 Apr 2014, Laurent Pinchart wrote:
> >>> On Wednesday 09 April 2014 15:05:26 Nicolas Pitre wrote:
> >>>> On Wed, 9 Apr 2014, Laurent Pinchart wrote:
> >>>>> Hello,
> >>>>>
> >>>>> (Resending due to a typo in an e-mail address that caused LAKML to
> >>>>> reject the mails. Sorry about the noise.)
> >>>>>
> >>>>> This patch set reworks Ezequiel Garcia's previous fix [1] of an out
> >>>>> of vmalloc space bug on PXA2[57]x platforms caused by an attempt to
> >>>>> map the start of physical uncached outside of the vmalloc space.
> >>>>>
> >>>>> This first three patches perform a couple of cleanups, and the last
> >>>>> patch fixes the problem. I've decided to map the memory at address
> >>>>> 0xfe000000 to minimize changes to the code, but this causes a bit
> >>>>> of fragmentation of vmalloc space. I could map it to the very end
> >>>>> of vmalloc space (0xfef00000) instead if preferred, which would
> >>>>> involve replacing a mov by an ldr in
> >>>>> pxa2[57]x_finish_suspend and pm_enter_standby_start.
> >>>>>
> >>>>> I've tested the patch set on a PXA270-based system.
> >>>>
> >>>> For those patches:
> >>>>
> >>>> Acked-by: Nicolas Pitre <nico@linaro.org>
> >>>
> >>> Thank you.
> >>>
> >>> MAINTAINERS lists three maintainers for the PXA architecture, and two
> >>> git trees that seem to be either dead or even deleted. Who picks up
> >>> patches for PXA ? Should I send a pull request ?
> >>
> >> If no one else answers, then just send a pull request to the ARM-SOC
> >> team (arm at kernel.org) and CC the linux-arm-kernel mailing list.
> >
> > What ever happened to this?
>
> Nothing, from the looks of it. I can apply them directly unless someone
> objects.
>
> Laurent, care to rebase and send a fresh copy? cc arm at kernel.org.
Sure. Done.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-07-11 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 18:08 [PATCH v3 0/4] ARM: pxa: Fix out of vmalloc space bug Laurent Pinchart
2014-04-09 18:08 ` [PATCH v3 1/4] ARM: pxa: Don't hardcode addresses and size in map_desc tables Laurent Pinchart
2014-04-09 18:08 ` [PATCH v3 2/4] ARM: pxa: Move UNCACHED_PHYS_0 mapping from generic.c to pxa2[57]x.c Laurent Pinchart
2014-04-09 18:08 ` [PATCH v3 3/4] ARM: pxa: pxa27x: Don't map IMEMC region statically Laurent Pinchart
2014-04-09 18:08 ` [PATCH v3 4/4] ARM: pxa: Move iotable mapping inside vmalloc region Laurent Pinchart
2014-04-09 19:05 ` [PATCH v3 0/4] ARM: pxa: Fix out of vmalloc space bug Nicolas Pitre
2014-04-11 0:14 ` Laurent Pinchart
2014-04-11 0:31 ` Nicolas Pitre
2014-07-10 12:10 ` Ezequiel Garcia
2014-07-10 16:56 ` Olof Johansson
2014-07-11 11:00 ` Laurent Pinchart [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=3632586.xKfZNAEmjS@avalon \
--to=laurent.pinchart@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox