From: Simon Horman <horms@kernel.org>
To: Guo Ren <guoren@kernel.org>
Cc: Chen Jiahao <chenjiahao16@huawei.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
conor.dooley@microchip.com, heiko@sntech.de, bjorn@rivosinc.com,
alex@ghiti.fr, akpm@linux-foundation.org, atishp@rivosinc.com,
bhe@redhat.com, thunder.leizhen@huawei.com
Subject: Re: [PATCH -next v3 1/2] riscv: kdump: Implement crashkernel=X,[high,low]
Date: Fri, 7 Apr 2023 14:03:52 +0200 [thread overview]
Message-ID: <ZDAGqL6CZGrL499u@kernel.org> (raw)
In-Reply-To: <CAJF2gTRtj=-XONv3cMZFd+qCtqUQqYZo5Lv7cgQbkGKTB0j7yg@mail.gmail.com>
On Fri, Apr 07, 2023 at 05:06:24PM +0800, Guo Ren wrote:
> On Thu, Apr 6, 2023 at 10:06 PM Chen Jiahao <chenjiahao16@huawei.com> 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.
> > Here introduce the parameter option crashkernel=X,[high,low].
> >
> > One can reserve the crash kernel from high memory above DMA zone range
> > by explicitly passing "crashkernel=X,high"; or reserve a memory range
> > below 4G with "crashkernel=X,low".
> Asked-by: Guo Ren <guoren@kernel.org>
Perhaps 'Acked-by' :)
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Guo Ren <guoren@kernel.org>
Cc: Chen Jiahao <chenjiahao16@huawei.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
conor.dooley@microchip.com, heiko@sntech.de, bjorn@rivosinc.com,
alex@ghiti.fr, akpm@linux-foundation.org, atishp@rivosinc.com,
bhe@redhat.com, thunder.leizhen@huawei.com
Subject: Re: [PATCH -next v3 1/2] riscv: kdump: Implement crashkernel=X,[high,low]
Date: Fri, 7 Apr 2023 14:03:52 +0200 [thread overview]
Message-ID: <ZDAGqL6CZGrL499u@kernel.org> (raw)
In-Reply-To: <CAJF2gTRtj=-XONv3cMZFd+qCtqUQqYZo5Lv7cgQbkGKTB0j7yg@mail.gmail.com>
On Fri, Apr 07, 2023 at 05:06:24PM +0800, Guo Ren wrote:
> On Thu, Apr 6, 2023 at 10:06 PM Chen Jiahao <chenjiahao16@huawei.com> 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.
> > Here introduce the parameter option crashkernel=X,[high,low].
> >
> > One can reserve the crash kernel from high memory above DMA zone range
> > by explicitly passing "crashkernel=X,high"; or reserve a memory range
> > below 4G with "crashkernel=X,low".
> Asked-by: Guo Ren <guoren@kernel.org>
Perhaps 'Acked-by' :)
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Guo Ren <guoren@kernel.org>
Cc: Chen Jiahao <chenjiahao16@huawei.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
conor.dooley@microchip.com, heiko@sntech.de, bjorn@rivosinc.com,
alex@ghiti.fr, akpm@linux-foundation.org, atishp@rivosinc.com,
bhe@redhat.com, thunder.leizhen@huawei.com
Subject: Re: [PATCH -next v3 1/2] riscv: kdump: Implement crashkernel=X,[high,low]
Date: Fri, 7 Apr 2023 14:03:52 +0200 [thread overview]
Message-ID: <ZDAGqL6CZGrL499u@kernel.org> (raw)
In-Reply-To: <CAJF2gTRtj=-XONv3cMZFd+qCtqUQqYZo5Lv7cgQbkGKTB0j7yg@mail.gmail.com>
On Fri, Apr 07, 2023 at 05:06:24PM +0800, Guo Ren wrote:
> On Thu, Apr 6, 2023 at 10:06 PM Chen Jiahao <chenjiahao16@huawei.com> 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.
> > Here introduce the parameter option crashkernel=X,[high,low].
> >
> > One can reserve the crash kernel from high memory above DMA zone range
> > by explicitly passing "crashkernel=X,high"; or reserve a memory range
> > below 4G with "crashkernel=X,low".
> Asked-by: Guo Ren <guoren@kernel.org>
Perhaps 'Acked-by' :)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-04-07 12:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 22:02 [PATCH -next v3 0/2] support allocating crashkernel above 4G explicitly on riscv Chen Jiahao
2023-04-06 22:02 ` Chen Jiahao
2023-04-06 22:02 ` Chen Jiahao
2023-04-06 22:02 ` [PATCH -next v3 1/2] riscv: kdump: Implement crashkernel=X,[high,low] Chen Jiahao
2023-04-06 22:02 ` Chen Jiahao
2023-04-06 22:02 ` Chen Jiahao
2023-04-07 9:06 ` Guo Ren
2023-04-07 9:06 ` Guo Ren
2023-04-07 9:06 ` Guo Ren
2023-04-07 12:03 ` Simon Horman [this message]
2023-04-07 12:03 ` Simon Horman
2023-04-07 12:03 ` Simon Horman
2023-04-11 1:38 ` Guo Ren
2023-04-11 1:38 ` Guo Ren
2023-04-11 1:38 ` Guo Ren
2023-04-07 12:03 ` Simon Horman
2023-04-07 12:03 ` Simon Horman
2023-04-07 12:03 ` Simon Horman
2023-04-07 12:58 ` Leizhen (ThunderTown)
2023-04-07 12:58 ` Leizhen (ThunderTown)
2023-04-07 12:58 ` Leizhen (ThunderTown)
2023-04-08 2:00 ` Leizhen (ThunderTown)
2023-04-08 2:00 ` Leizhen (ThunderTown)
2023-04-08 2:00 ` Leizhen (ThunderTown)
2023-04-10 9:52 ` chenjiahao (C)
2023-04-10 9:52 ` chenjiahao (C)
2023-04-10 9:52 ` chenjiahao (C)
2023-04-10 9:20 ` chenjiahao (C)
2023-04-10 9:20 ` chenjiahao (C)
2023-04-10 9:20 ` chenjiahao (C)
2023-04-06 22:02 ` [PATCH -next v3 2/2] docs: kdump: Update the crashkernel description for riscv Chen Jiahao
2023-04-06 22:02 ` Chen Jiahao
2023-04-06 22:02 ` Chen Jiahao
2023-04-07 8:34 ` Guo Ren
2023-04-07 8:34 ` Guo Ren
2023-04-07 8:34 ` Guo Ren
2023-04-07 12:04 ` Simon Horman
2023-04-07 12:04 ` Simon Horman
2023-04-07 12:04 ` Simon Horman
2023-04-08 2:01 ` Leizhen (ThunderTown)
2023-04-08 2:01 ` Leizhen (ThunderTown)
2023-04-08 2:01 ` Leizhen (ThunderTown)
2023-04-07 12:05 ` [PATCH -next v3 0/2] support allocating crashkernel above 4G explicitly on riscv Simon Horman
2023-04-07 12:05 ` Simon Horman
2023-04-07 12:05 ` Simon Horman
2023-04-10 10:02 ` chenjiahao (C)
2023-04-10 10:02 ` chenjiahao (C)
2023-04-10 10:02 ` chenjiahao (C)
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=ZDAGqL6CZGrL499u@kernel.org \
--to=horms@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=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 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.