linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: ignore memory outside of the linear range
Date: Mon, 24 Aug 2015 10:22:56 +0100	[thread overview]
Message-ID: <20150824092256.GA11262@arm.com> (raw)
In-Reply-To: <CAKv+Gu-OQ4VyCqe=mEDOrrfAtAWTfRtAiqXMGSVjJxOH6xi4Ow@mail.gmail.com>

On Mon, Aug 24, 2015 at 09:00:43AM +0100, Ard Biesheuvel wrote:
> >> This is a followup to the single patch I posted on Aug 15th to ignore
> >> RAM that cannot be covered by the linear mapping. Instead of clipping
> >> the memory after the fact, this clips the memory before installing the
> >> regions into the memblock memory table.
> >>
> >> This is basically the approach that Mark Rutland suggested here
> >>
> >> http://article.gmane.org/gmane.linux.ports.arm.kernel/430239
> >>
> >> but modified to correctly consider the base of the kernel image as the
> >> start of the linear mapping.
> >>
> >> Ard Biesheuvel (2):
> >>   of/fdt: make memblock maximum physical address arch configurable
> >>   arm64: set MAX_MEMBLOCK_ADDR according to linear region size
> >>
> >>  arch/arm64/include/asm/memory.h |  8 ++++++++
> >>  drivers/of/fdt.c                | 12 +++++++-----
> >>  2 files changed, 15 insertions(+), 5 deletions(-)
> >
> > Tested on Freescale LS2085ARDB which has a split memory region
> > that triggers the bug.
> >
> > Tested-by: Stuart Yoder <stuart.yoder@freescale.com>
> >
> 
> Will you be picking up this series for v4.3? If so, do you need me to
> resend it with the tags added?

Sorry, I missed Rob's ack on the of/fdt.c change. I'll pick these up
later today, no need to resend.

Cheers,

Will

  reply	other threads:[~2015-08-24  9:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  9:34 [PATCH 0/2] arm64: ignore memory outside of the linear range Ard Biesheuvel
2015-08-18  9:34 ` [PATCH 1/2] of/fdt: make memblock maximum physical address arch configurable Ard Biesheuvel
2015-08-20  9:18   ` Catalin Marinas
2015-08-23 22:01   ` Rob Herring
2015-08-18  9:34 ` [PATCH 2/2] arm64: set MAX_MEMBLOCK_ADDR according to linear region size Ard Biesheuvel
2015-08-18 10:00   ` Will Deacon
2015-08-18 10:04     ` Ard Biesheuvel
2015-08-18 17:39       ` Catalin Marinas
2015-08-18 17:44         ` Ard Biesheuvel
2015-08-19  9:15           ` Catalin Marinas
2015-08-20  5:09         ` Ard Biesheuvel
2015-08-20  9:17           ` Catalin Marinas
2015-08-18 14:24     ` Catalin Marinas
2015-08-18 14:31       ` Ard Biesheuvel
2015-08-18 14:38         ` Ard Biesheuvel
2015-08-18 14:51       ` Russell King - ARM Linux
2015-08-18 16:16         ` Catalin Marinas
2015-08-20  9:19   ` Catalin Marinas
2015-08-20 11:54     ` Ard Biesheuvel
2015-08-20 12:50       ` Catalin Marinas
2015-08-18 14:18 ` [PATCH 0/2] arm64: ignore memory outside of the linear range Stuart Yoder
2015-08-24  8:00   ` Ard Biesheuvel
2015-08-24  9:22     ` Will Deacon [this message]
2015-08-24 13:58       ` Stuart Yoder
2015-08-24 14:08         ` Will Deacon
2015-08-24 22:34           ` Stuart Yoder
2015-08-25  9:45             ` Ard Biesheuvel
2015-08-25  9:54               ` Russell King - ARM Linux
2015-08-25 10:02               ` Will Deacon
2015-08-25 10:10                 ` Ard Biesheuvel

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=20150824092256.GA11262@arm.com \
    --to=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).