linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Guanghui Feng <guanghuifeng@linux.alibaba.com>,
	<baolin.wang@linux.alibaba.com>, <catalin.marinas@arm.com>,
	<will@kernel.org>, <akpm@linux-foundation.org>,
	<david@redhat.com>, <jianyong.wu@arm.com>, <james.morse@arm.com>,
	<quic_qiancai@quicinc.com>, <christophe.leroy@csgroup.eu>,
	<jonathan@marek.ca>, <mark.rutland@arm.com>,
	<chenzhou10@huawei.com>, <anshuman.khandual@arm.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <rppt@kernel.org>,
	<geert+renesas@glider.be>, <ardb@kernel.org>,
	<linux-mm@kvack.org>
Subject: Re: [PATCH] arm64: mm: fix linear mapping mem access performace degradation
Date: Tue, 28 Jun 2022 09:40:32 +0800	[thread overview]
Message-ID: <ad348d23-6e7f-f66b-07bc-60e57d15c441@huawei.com> (raw)
In-Reply-To: <1656241815-28494-1-git-send-email-guanghuifeng@linux.alibaba.com>



On 2022/6/26 19:10, Guanghui Feng wrote:
> +void __init mapping_crashkernel(void)
> +{
> +	if (can_set_direct_map() || IS_ENABLED(CONFIG_KFENCE))
> +	    return;
> +
> +	if (!crash_mem_map || !crashk_res.end)
> +	    return;

All the code related to crash_mem_map can be removed now.

> +
> +	map_crashkernel(swapper_pg_dir, crashk_res.start,
> +			crashk_res.end + 1, PAGE_KERNEL,
> +			NO_BLOCK_MAPPINGS | NO_CONT_MAPPINGS);
> +}

-- 
Regards,
  Zhen Lei

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2022-06-28  1:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26 11:10 [PATCH] arm64: mm: fix linear mapping mem access performace degradation Guanghui Feng
2022-06-27  6:34 ` Mike Rapoport
     [not found]   ` <4d18d303-aeed-0beb-a8a4-32893f2d438d@linux.alibaba.com>
2022-06-27  9:49     ` Mike Rapoport
2022-06-27 10:46       ` guanghui.fgh
2022-06-27 12:06         ` Leizhen (ThunderTown)
2022-06-27 12:25           ` guanghui.fgh
2022-06-28  1:34             ` Leizhen (ThunderTown)
2022-06-28  3:06               ` guanghui.fgh
2022-06-28  6:21                 ` Leizhen (ThunderTown)
2022-06-28  7:52                 ` guanghui.fgh
2022-06-27 16:49         ` Mike Rapoport
2022-06-28  1:50           ` Kefeng Wang
2022-06-28  3:22             ` guanghui.fgh
2022-06-28  2:55           ` guanghui.fgh
2022-06-28  1:40 ` Leizhen (ThunderTown) [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=ad348d23-6e7f-f66b-07bc-60e57d15c441@huawei.com \
    --to=thunder.leizhen@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=catalin.marinas@arm.com \
    --cc=chenzhou10@huawei.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=david@redhat.com \
    --cc=geert+renesas@glider.be \
    --cc=guanghuifeng@linux.alibaba.com \
    --cc=james.morse@arm.com \
    --cc=jianyong.wu@arm.com \
    --cc=jonathan@marek.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=quic_qiancai@quicinc.com \
    --cc=rppt@kernel.org \
    --cc=will@kernel.org \
    /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).