From: Baoquan He <bhe@redhat.com>
To: Jiri Bohac <jbohac@suse.cz>
Cc: Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
kexec@lists.infradead.org, Philipp Rudo <prudo@redhat.com>,
Donald Dutile <ddutile@redhat.com>,
Pingfan Liu <piliu@redhat.com>, Tao Liu <ltao@redhat.com>,
linux-kernel@vger.kernel.org,
David Hildenbrand <dhildenb@redhat.com>,
Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH v4 5/5] x86: implement crashkernel cma reservation
Date: Tue, 3 Jun 2025 19:02:06 +0800 [thread overview]
Message-ID: <aD7WLv86BOVS+GPm@MiWiFi-R3L-srv> (raw)
In-Reply-To: <aDoVhDc11ZcJyHm2@dwarf.suse.cz>
On 05/30/25 at 10:31pm, Jiri Bohac wrote:
......snip..
> @@ -582,7 +582,7 @@ static void __init arch_reserve_crashkernel(void)
>
> ret = parse_crashkernel(boot_command_line, memblock_phys_mem_size(),
> &crash_size, &crash_base,
> - &low_size, NULL, &high);
> + &low_size, &cma_size, &high);
> if (ret)
> return;
>
> @@ -592,6 +592,7 @@ static void __init arch_reserve_crashkernel(void)
> }
>
> reserve_crashkernel_generic(crash_size, crash_base, low_size, high);
> + reserve_crashkernel_cma(cma_size);
Wondering if ,high|low is still allowed (or needed) when ,cma is specified.
next prev parent reply other threads:[~2025-06-03 11:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 20:23 [PATCH v4 0/5] kdump: crashkernel reservation from CMA Jiri Bohac
2025-05-30 20:26 ` [PATCH v4 1/5] Add a new optional ",cma" suffix to the crashkernel= command line option Jiri Bohac
2025-05-30 20:27 ` [PATCH v4 2/5] kdump: implement reserve_crashkernel_cma Jiri Bohac
2025-05-30 20:28 ` [PATCH v4 3/5] kdump, documentation: describe craskernel CMA reservation Jiri Bohac
2025-05-30 20:29 ` [PATCH v4 4/5] kdump: wait for DMA to finish when using CMA Jiri Bohac
2025-06-03 13:15 ` David Hildenbrand
2025-06-03 15:59 ` Jiri Bohac
2025-06-03 16:25 ` David Hildenbrand
2025-06-04 7:40 ` Jiri Bohac
2025-06-04 7:42 ` David Hildenbrand
2025-06-04 8:15 ` [PATCH v5 " Jiri Bohac
2025-05-30 20:31 ` [PATCH v4 5/5] x86: implement crashkernel cma reservation Jiri Bohac
2025-06-03 11:02 ` Baoquan He [this message]
2025-06-03 12:11 ` Jiri Bohac
2025-06-03 12:56 ` Baoquan He
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=aD7WLv86BOVS+GPm@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=ddutile@redhat.com \
--cc=dhildenb@redhat.com \
--cc=dyoung@redhat.com \
--cc=jbohac@suse.cz \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltao@redhat.com \
--cc=mhocko@suse.cz \
--cc=piliu@redhat.com \
--cc=prudo@redhat.com \
--cc=vgoyal@redhat.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