[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<170578499750.24348.2518240009884006018.git-patchwork-notify@kernel.org>
Date: Sat, 20 Jan 2024 21:09:57 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Baoquan He <bhe@...hat.com>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
kexec@...ts.infradead.org, x86@...nel.org, linux-parisc@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org,
akpm@...ux-foundation.org, ebiederm@...ssion.com, takahiro.akashi@...aro.org
Subject: Re: [PATCH 0/2] kexec_file: Load kernel at top of system RAM if required
Hello:
This series was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@...ux-foundation.org>:
On Tue, 14 Nov 2023 17:16:56 +0800 you wrote:
> Justification:
> ==============
> Kexec_load interface has been doing top down searching and loading
> kernel/initrd/purgtory etc to prepare for kexec reboot. In that way,
> the benefits are that it avoids to consume and fragment limited low
> memory which satisfy DMA buffer allocation and big chunk of continuous
> memory during system init; and avoids to stir with BIOS/FW reserved
> or occupied areas, or corner case handling/work around/quirk occupied
> areas when doing system init. By the way, the top-down searching and
> loading of kexec-ed kernel is done in user space utility code.
>
> [...]
Here is the summary with links:
- [1/2] resource: add walk_system_ram_res_rev()
(no matching commit)
- [2/2] kexec_file: Load kernel at top of system RAM if required
https://git.kernel.org/riscv/c/b3ba234171cd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists