From: Baoquan He <bhe@redhat.com>
To: "Leizhen (ThunderTown)" <thunder.leizhen@huaweicloud.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
catalin.marinas@arm.com, thunder.leizhen@huawei.com,
dyoung@redhat.com, prudo@redhat.com, samuel.holland@sifive.com,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
x86@kernel.org
Subject: Re: [PATCH v2 3/8] crash_core: change parse_crashkernel() to support crashkernel=,high|low parsing
Date: Mon, 11 Sep 2023 10:11:16 +0800 [thread overview]
Message-ID: <ZP53RL/6PdxLLh7a@MiWiFi-R3L-srv> (raw)
In-Reply-To: <58a0c4be-0302-04e0-8723-df37407884a8@huaweicloud.com>
On 09/06/23 at 05:07pm, Leizhen (ThunderTown) wrote:
>
>
> On 2023/9/5 16:29, Baoquan He wrote:
> > On 09/04/23 at 10:47am, Leizhen (ThunderTown) wrote:
> >>
> >>
> >> On 2023/9/1 17:49, Baoquan He wrote:
> >>>>> +
> >>>>> + *high = true;
> >>>>> + } else if (ret || !*crash_size) {
> >>>> This check can be moved outside of #ifdef. Because even '!high', it's completely
> >>>> applicable. The overall adjustment is as follows:
> >>> Hmm, the current logic is much easier to understand. However, I may not
> >>> 100% get your suggestion. Can you paste the complete code in your
> >>> suggested way? Do not need 100% correct code, just the skeleton of code logic
> >>> so that I can better understand it and add inline comment.
> >>
> >> int __init parse_crashkernel(...)
> >> {
> >> int ret;
> >>
> >> /* crashkernel=X[@offset] */
> >> ret = __parse_crashkernel(cmdline, system_ram, crash_size,
> >> crash_base, NULL);
> >>
> >> #ifdef CONFIG_ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION
> >> if (high && ret == -ENOENT) {
> >> ... ... //The code for your original branch "else if (ret == -ENOENT) {"
> >> ret = 0; //Added based on the next discussion
> >> }
> >> +#endif
> >>
> >> if (!*crash_size)
> >> ret = -EINVAL;
> >>
> >> return ret;
> >> }
> >>
> > Thanks, Zhen Lei.
> >
> > I paste the whole parse_crashkernel() as you suggested at bottom. Please
> > check if it's what you want.
>
> Yes.
>
> > To me, both is fine to me. I have two minor
> > concerns to your suggested way.
> >
> > 1)
> > I took the "if (!high) return" way because except of x86/arm64, all
> > other architectures will call parse_crashkerne() and check
> > if *crash_size ==0. Please try 'git grep "parse_crashkernel(" arch'
> > and check those call sites. With that, we will have duplicated checking.
>
> Add some patches to remove the duplicated checking of other ARCHs? After this
> patch series upstreamed.
I resisted this in the first place, after rethinking, it makes sense.
parse_crashkernel() returning 0 indicates a meaningful crashkernel vlaue
parsed, otherwise non-zero. I will go with this.
>
> >
> > ret = __parse_crashkernel(cmdline, system_ram, crash_size,
> > crash_base, NULL);
> > if (!high)
> > return ret;
> > 2)
> > I actually like below branch and the code comment. It can give people
> > hint about what's going on in that case. Discarding it is a little pity.
>
> Except that "!*crash_size" and "(high && ret == -ENOENT)" needs special comments,
> other common errors do not need to be described, I think. Even if some is required,
> it should be placed in function __parse_crashkernel().
Hmm, I will consider how to comment these better, will update and post
v3.
Thanks, Lei.
>
> >
> > } else if (ret || !*crash_size) {
> > /* The specified value is invalid */
> > return -1;
> > }
> >
> > int __init parse_crashkernel(...)
> > {
> > int ret;
> >
> > /* crashkernel=X[@offset] */
> > ret = __parse_crashkernel(cmdline, system_ram, crash_size,
> > crash_base, NULL);
> > #ifdef CONFIG_ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION
> > if (high && ret == -ENOENT) {
> > ret = __parse_crashkernel(cmdline, 0, crash_size,
> > crash_base, suffix_tbl[SUFFIX_HIGH]);
> > if (ret || !*crash_size)
> > return -EINVAL;
> >
> > /*
> > * crashkernel=Y,low can be specified or not, but invalid value
> > * is not allowed.
> > */
> > ret = __parse_crashkernel(cmdline, 0, low_size,
> > crash_base, suffix_tbl[SUFFIX_LOW]);
> > if (ret == -ENOENT) {
> > *low_size = DEFAULT_CRASH_KERNEL_LOW_SIZE;
> > ret = 0;
> > } else if (ret) {
> > return ret;
> > }
> >
> > *high = true;
> > }
> > #endif
> >
> > if (!*crash_size)
> > ret = -EINVAL;
> >
> > return ret;
> > }
> >
> > .
> >
>
> --
> Regards,
> Zhen Lei
>
next prev parent reply other threads:[~2023-09-11 2:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 12:16 [PATCH v2 0/8] kdump: use generic functions to simplify crashkernel reservation in arch Baoquan He
2023-08-29 12:16 ` [PATCH v2 1/8] crash_core.c: remove unnecessary parameter of function Baoquan He
2023-08-31 1:25 ` Leizhen (ThunderTown)
2023-08-29 12:16 ` [PATCH v2 2/8] crash_core: change the prototype of function parse_crashkernel() Baoquan He
2023-08-31 2:30 ` Leizhen (ThunderTown)
2023-08-29 12:16 ` [PATCH v2 3/8] crash_core: change parse_crashkernel() to support crashkernel=,high|low parsing Baoquan He
2023-08-31 2:56 ` Leizhen (ThunderTown)
2023-09-01 9:49 ` Baoquan He
2023-09-04 2:47 ` Leizhen (ThunderTown)
2023-09-05 8:29 ` Baoquan He
2023-09-06 9:07 ` Leizhen (ThunderTown)
2023-09-11 2:11 ` Baoquan He [this message]
2023-08-29 12:16 ` [PATCH v2 4/8] crash_core: add generic function to do reservation Baoquan He
2023-08-31 3:23 ` Leizhen (ThunderTown)
2023-09-01 10:08 ` Baoquan He
2023-08-29 12:16 ` [PATCH v2 5/8] crash_core.h: include <asm/crash_core.h> if generic reservation is needed Baoquan He
2023-08-29 12:16 ` [PATCH v2 6/8] x86: kdump: use generic interface to simplify crashkernel reservation code Baoquan He
2023-08-29 21:37 ` kernel test robot
2023-08-30 1:49 ` kernel test robot
2023-08-30 11:39 ` Baoquan He
2023-08-31 3:43 ` Leizhen (ThunderTown)
2023-09-01 10:10 ` Baoquan He
2023-08-29 12:16 ` [PATCH v2 7/8] arm64: kdump: use generic interface to simplify crashkernel reservation Baoquan He
2023-08-31 3:51 ` Leizhen (ThunderTown)
2023-08-29 12:16 ` [PATCH v2 8/8] crash_core.c: remove unneeded functions Baoquan He
2023-08-31 3:51 ` Leizhen (ThunderTown)
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=ZP53RL/6PdxLLh7a@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prudo@redhat.com \
--cc=samuel.holland@sifive.com \
--cc=thunder.leizhen@huawei.com \
--cc=thunder.leizhen@huaweicloud.com \
--cc=x86@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