All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] arm64 initrd mapping/relocation
Date: Tue, 2 Feb 2016 18:06:22 +0000	[thread overview]
Message-ID: <20160202180622.GP10166@arm.com> (raw)
In-Reply-To: <1454435802-7604-1-git-send-email-ard.biesheuvel@linaro.org>

On Tue, Feb 02, 2016 at 06:56:39PM +0100, Ard Biesheuvel wrote:
> After discussing in linux-efi with Mark, and on #armlinux with Will, this is
> a proposal for dealing with initrd memory that is potentially not covered by
> the linear region.
> 
> Note that this will look slightly differently when some of the KASLR work gets
> merged, but this should only affect the way we deal with the initrd if it sits
> outside of the linear region.
> 
> Mostly intended for discussion, not tested at all.

Thanks Ard, this looks like a much better approach to me. Mark -- does
the general idea work for you too?

Will

  parent reply	other threads:[~2016-02-02 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 17:56 [RFC PATCH 0/3] arm64 initrd mapping/relocation Ard Biesheuvel
2016-02-02 17:56 ` [RFC PATCH 1/3] memblock: add routine to clear the MEMBLOCK_NOMAP flag for a region Ard Biesheuvel
2016-02-02 17:56 ` [RFC PATCH 2/3] arm64: add the initrd region to the linear mapping explicitly Ard Biesheuvel
2016-02-02 17:56 ` [RFC PATCH 3/3] arm64: remove the now unneeded relocate_initrd() Ard Biesheuvel
2016-02-02 18:06 ` Will Deacon [this message]
2016-02-02 21:39   ` [RFC PATCH 0/3] arm64 initrd mapping/relocation Mark Langsdorf
2016-02-03 14:22   ` Mark Salter
2016-02-03 14:26     ` Ard Biesheuvel
2016-02-08 16:17       ` Jeremy Linton
2016-02-02 21:39 ` Mark Langsdorf
2016-02-03  8:42   ` 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=20160202180622.GP10166@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 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.