From: Will Deacon <will@kernel.org>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
thunder.leizhen@huawei.com, horms@kernel.org,
John.p.donnelly@oracle.com, linux-arm-kernel@lists.infradead.org,
ardb@kernel.org, rppt@kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v2 0/3] arm64: kdump : take off the protection on crashkernel memory region
Date: Tue, 11 Apr 2023 19:37:24 +0100 [thread overview]
Message-ID: <168123748697.3041682.15156562269597498270.b4-ty@kernel.org> (raw)
In-Reply-To: <20230407011507.17572-1-bhe@redhat.com>
On Fri, 7 Apr 2023 09:15:04 +0800, Baoquan He wrote:
> Problem:
> =======
> On arm64, block and section mapping is supported to build page tables.
> However, currently it enforces to take base page mapping for the whole
> linear mapping if CONFIG_ZONE_DMA or CONFIG_ZONE_DMA32 is enabled and
> crashkernel kernel parameter is set. This will cause longer time of the
> linear mapping process during bootup and severe performance degradation
> during running time.
>
> [...]
Applied to arm64 (for-next/kdump), thanks!
[1/3] arm64: kdump : take off the protection on crashkernel memory region
https://git.kernel.org/arm64/c/0d124e96051b
[2/3] arm64: kdump: do not map crashkernel region specifically
https://git.kernel.org/arm64/c/04a2a7af3d97
[3/3] arm64: kdump: defer the crashkernel reservation for platforms with no DMA memory zones
https://git.kernel.org/arm64/c/504cae453f82
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-04-11 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 1:15 Baoquan He
2023-04-07 1:15 ` [PATCH v2 1/3] " Baoquan He
2023-04-07 1:15 ` [PATCH v2 2/3] arm64: kdump: do not map crashkernel region specifically Baoquan He
2023-04-07 1:15 ` [PATCH v2 3/3] arm64: kdump: defer the crashkernel reservation for platforms with no DMA memory zones Baoquan He
2023-04-11 18:37 ` 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=168123748697.3041682.15156562269597498270.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=John.p.donnelly@oracle.com \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=horms@kernel.org \
--cc=kernel-team@android.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--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
all inboxes | Powered by JetHome®