From: Borislav Petkov <bp@alien8.de>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: tglx@linutronix.de, mingo@redhat.com, ebiederm@xmission.com,
rppt@linux.ibm.com, catalin.marinas@arm.com, will.deacon@arm.com,
akpm@linux-foundation.org, ard.biesheuvel@linaro.org,
horms@verge.net.au, takahiro.akashi@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org, wangkefeng.wang@huawei.com
Subject: Re: [RESEND PATCH v5 0/4] support reserving crashkernel above 4G on arm64 kdump
Date: Tue, 16 Apr 2019 15:15:49 +0200 [thread overview]
Message-ID: <20190416131549.GD31772@zn.tnic> (raw)
In-Reply-To: <20190416113519.90507-1-chenzhou10@huawei.com>
On Tue, Apr 16, 2019 at 07:35:15PM +0800, Chen Zhou wrote:
> When crashkernel is reserved above 4G in memory, kernel should reserve
> some amount of low memory for swiotlb and some DMA buffers. So there may
> be two crash kernel regions, one is below 4G, the other is above 4G.
>
> Crash dump kernel reads more than one crash kernel regions via a dtb
> property under node /chosen,
> linux,usable-memory-range = <BASE1 SIZE1 [BASE2 SIZE2]>.
Can you please not flood everyone with this patchset every day, and
today twice?
This is not the frequency with how you send patchsets upstream. See
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#don-t-get-discouraged-or-impatient
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2019-04-16 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 11:35 Chen Zhou
2019-04-16 11:35 ` [RESEND PATCH v5 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c Chen Zhou
2019-04-16 11:35 ` [RESEND PATCH v5 2/4] arm64: kdump: support reserving crashkernel above 4G Chen Zhou
2019-04-16 11:35 ` [RESEND PATCH v5 3/4] memblock: extend memblock_cap_memory_range to multiple ranges Chen Zhou
2019-04-16 11:35 ` [RESEND PATCH v5 4/4] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2019-04-16 13:15 ` Borislav Petkov [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=20190416131549.GD31772@zn.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=chenzhou10@huawei.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rppt@linux.ibm.com \
--cc=takahiro.akashi@linaro.org \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
--cc=will.deacon@arm.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