From: Will Deacon <will@kernel.org>
To: AKASHI Takahiro <takahiro.akashi@linaro.org>,
Benjamin Gwin <bgwin@google.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
Ryan O'Leary <ryanoleary@google.com>
Subject: Re: [PATCH v2] arm64: kexec_file: try more regions if loading segments fails
Date: Thu, 5 Nov 2020 22:06:40 +0000 [thread overview]
Message-ID: <160461288596.2517909.5557459211305351671.b4-ty@kernel.org> (raw)
In-Reply-To: <20201103201106.2397844-1-bgwin@google.com>
On Tue, 3 Nov 2020 12:11:06 -0800, Benjamin Gwin wrote:
> It's possible that the first region picked for the new kernel will make
> it impossible to fit the other segments in the required 32GB window,
> especially if we have a very large initrd.
>
> Instead of giving up, we can keep testing other regions for the kernel
> until we find one that works.
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: kexec_file: try more regions if loading segments fails
https://git.kernel.org/arm64/c/108aa503657e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-05 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 18:18 [PATCH] arm64: kexec_file: try more regions if loading segments fails Benjamin Gwin
2020-11-03 20:11 ` [PATCH v2] " Benjamin Gwin
2020-11-05 22:06 ` Will Deacon [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=160461288596.2517909.5557459211305351671.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=bgwin@google.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ryanoleary@google.com \
--cc=takahiro.akashi@linaro.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.