From: patchwork-bot+linux-riscv@kernel.org
To: chenjiahao (C) <chenjiahao16@huawei.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
conor.dooley@microchip.com, guoren@kernel.org, heiko@sntech.de,
bjorn@rivosinc.com, alex@ghiti.fr, akpm@linux-foundation.org,
atishp@rivosinc.com, bhe@redhat.com, thunder.leizhen@huawei.com,
horms@kernel.org
Subject: Re: [PATCH -next v9 0/2] support allocating crashkernel above 4G explicitly on riscv
Date: Wed, 30 Aug 2023 13:20:34 +0000 [thread overview]
Message-ID: <169340163484.19859.603263749901327950.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230726175000.2536220-1-chenjiahao16@huawei.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 26 Jul 2023 17:49:58 +0000 you wrote:
> On riscv, the current crash kernel allocation logic is trying to
> allocate within 32bit addressible memory region by default, if
> failed, try to allocate without 4G restriction.
>
> In need of saving DMA zone memory while allocating a relatively large
> crash kernel region, allocating the reserved memory top down in
> high memory, without overlapping the DMA zone, is a mature solution.
> Hence this patchset introduces the parameter option crashkernel=X,[high,low].
>
> [...]
Here is the summary with links:
- [-next,v9,1/2] riscv: kdump: Implement crashkernel=X,[high,low]
https://git.kernel.org/riscv/c/5882e5acf18d
- [-next,v9,2/2] docs: kdump: Update the crashkernel description for riscv
https://git.kernel.org/riscv/c/33f0dd973d4e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-30 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 17:49 [PATCH -next v9 0/2] support allocating crashkernel above 4G explicitly on riscv Chen Jiahao
2023-07-26 17:49 ` [PATCH -next v9 1/2] riscv: kdump: Implement crashkernel=X,[high,low] Chen Jiahao
2023-07-26 10:24 ` Baoquan He
2023-07-26 17:50 ` [PATCH -next v9 2/2] docs: kdump: Update the crashkernel description for riscv Chen Jiahao
2023-07-26 10:25 ` Baoquan He
2023-08-29 9:54 ` [PATCH -next v9 0/2] support allocating crashkernel above 4G explicitly on riscv chenjiahao (C)
2023-08-30 13:20 ` patchwork-bot+linux-riscv [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=169340163484.19859.603263749901327950.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=atishp@rivosinc.com \
--cc=bhe@redhat.com \
--cc=bjorn@rivosinc.com \
--cc=chenjiahao16@huawei.com \
--cc=conor.dooley@microchip.com \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=horms@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=thunder.leizhen@huawei.com \
/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).