All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Will Deacon <will@kernel.org>,
	Zhen Lei <thunder.leizhen@huawei.com>,
	Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
	linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Cc: Chen Zhou <dingguo.cz@antgroup.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	John Donnelly <John.p.donnelly@oracle.com>,
	Dave Kleikamp <dave.kleikamp@oracle.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>,
	Feng Zhou <zhoufeng.zf@bytedance.com>,
	"Eric W . Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] arm64: kdump: Do not allocate crash low memory if not needed
Date: Mon, 16 May 2022 20:06:51 +0100	[thread overview]
Message-ID: <165272800400.3869992.18113408678309495430.b4-ty@arm.com> (raw)
In-Reply-To: <20220511032033.426-1-thunder.leizhen@huawei.com>

On Wed, 11 May 2022 11:20:32 +0800, Zhen Lei wrote:
> When "crashkernel=X,high" is specified, the specified "crashkernel=Y,low"
> memory is not required in the following corner cases:
> 1. If both CONFIG_ZONE_DMA and CONFIG_ZONE_DMA32 are disabled, it means
>    that the devices can access any memory.
> 2. If the system memory is small, the crash high memory may be allocated
>    from the DMA zones. If that happens, there's no need to allocate
>    another crash low memory because there's already one.
> 
> [...]

Applied to arm64 (for-next/crashkernel), thanks!

[1/1] arm64: kdump: Do not allocate crash low memory if not needed
      https://git.kernel.org/arm64/c/8f0f104e2ab6

-- 
Catalin


WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Will Deacon <will@kernel.org>,
	Zhen Lei <thunder.leizhen@huawei.com>,
	Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
	linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Cc: Chen Zhou <dingguo.cz@antgroup.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	John Donnelly <John.p.donnelly@oracle.com>,
	Dave Kleikamp <dave.kleikamp@oracle.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>,
	Feng Zhou <zhoufeng.zf@bytedance.com>,
	"Eric W . Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] arm64: kdump: Do not allocate crash low memory if not needed
Date: Mon, 16 May 2022 20:06:51 +0100	[thread overview]
Message-ID: <165272800400.3869992.18113408678309495430.b4-ty@arm.com> (raw)
In-Reply-To: <20220511032033.426-1-thunder.leizhen@huawei.com>

On Wed, 11 May 2022 11:20:32 +0800, Zhen Lei wrote:
> When "crashkernel=X,high" is specified, the specified "crashkernel=Y,low"
> memory is not required in the following corner cases:
> 1. If both CONFIG_ZONE_DMA and CONFIG_ZONE_DMA32 are disabled, it means
>    that the devices can access any memory.
> 2. If the system memory is small, the crash high memory may be allocated
>    from the DMA zones. If that happens, there's no need to allocate
>    another crash low memory because there's already one.
> 
> [...]

Applied to arm64 (for-next/crashkernel), thanks!

[1/1] arm64: kdump: Do not allocate crash low memory if not needed
      https://git.kernel.org/arm64/c/8f0f104e2ab6

-- 
Catalin


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

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: kexec@lists.infradead.org
Subject: [PATCH] arm64: kdump: Do not allocate crash low memory if not needed
Date: Mon, 16 May 2022 20:06:51 +0100	[thread overview]
Message-ID: <165272800400.3869992.18113408678309495430.b4-ty@arm.com> (raw)
In-Reply-To: <20220511032033.426-1-thunder.leizhen@huawei.com>

On Wed, 11 May 2022 11:20:32 +0800, Zhen Lei wrote:
> When "crashkernel=X,high" is specified, the specified "crashkernel=Y,low"
> memory is not required in the following corner cases:
> 1. If both CONFIG_ZONE_DMA and CONFIG_ZONE_DMA32 are disabled, it means
>    that the devices can access any memory.
> 2. If the system memory is small, the crash high memory may be allocated
>    from the DMA zones. If that happens, there's no need to allocate
>    another crash low memory because there's already one.
> 
> [...]

Applied to arm64 (for-next/crashkernel), thanks!

[1/1] arm64: kdump: Do not allocate crash low memory if not needed
      https://git.kernel.org/arm64/c/8f0f104e2ab6

-- 
Catalin



  parent reply	other threads:[~2022-05-16 19:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  3:20 [PATCH] arm64: kdump: Do not allocate crash low memory if not needed Zhen Lei
2022-05-11  3:20 ` Zhen Lei
2022-05-11  3:20 ` Zhen Lei
2022-05-11  9:06 ` Baoquan He
2022-05-11  9:06   ` Baoquan He
2022-05-11  9:06   ` Baoquan He
2022-05-11  9:50   ` Leizhen (ThunderTown)
2022-05-11  9:50     ` Leizhen
2022-05-11  9:50     ` Leizhen (ThunderTown)
2022-05-11 10:06     ` Baoquan He
2022-05-11 10:06       ` Baoquan He
2022-05-11 10:06       ` Baoquan He
2022-05-16 19:06 ` Catalin Marinas [this message]
2022-05-16 19:06   ` Catalin Marinas
2022-05-16 19:06   ` Catalin Marinas

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=165272800400.3869992.18113408678309495430.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=John.p.donnelly@oracle.com \
    --cc=bhe@redhat.com \
    --cc=corbet@lwn.net \
    --cc=dave.kleikamp@oracle.com \
    --cc=dingguo.cz@antgroup.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=thunder.leizhen@huawei.com \
    --cc=vgoyal@redhat.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@kernel.org \
    --cc=zhoufeng.zf@bytedance.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.