public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric DeVolder <eric_devolder@yahoo.com>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org
Cc: kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
	linux-s390@vger.kernel.org, akpm@linux-foundation.org,
	ignat@cloudflare.com
Subject: Re: [PATCH 0/3] kernel/Kconfig.kexec: drop select of KEXEC for CRASH_DUMP
Date: Sat, 25 Nov 2023 18:07:29 -0600	[thread overview]
Message-ID: <5ab45f48-9ec2-4611-81a2-4dc2f1854c4f@yahoo.com> (raw)
In-Reply-To: <20231123073652.507034-1-bhe@redhat.com>


On 11/23/23 01:36, Baoquan He wrote:
> Ignat reported a potential config regression was introduced by
> commit 89cde455915f ("kexec: consolidate kexec and crash options
> into kernel/Kconfig.kexec"). Please click below link for more details:
>
> https://lore.kernel.org/all/CALrw=nHpRQQaQTP_jZfREgrQEMpS8jBF8JQCv4ygqXycE-StaA@mail.gmail.com/T/#u
>
> The patch 1 fix the regression by removing incorrect CONFIG_KEXEC
> ifdeffery scope adding in arm's <asm/kexec.h>, then dropping the
> select of KEXEC for CRASH_DUMP. This is tested and passed a cross
> comiping of arm.
>
> Patch 2 is to fix a build failure when I tested patch 1 on x86_64, the
> wrong CONFIG_KEXEC iddeffery is replaced with CONFIG_KEXEC_CORE. Test
> passed on x86_64.
>
> Patch 3 is to fix an unnecessary 'select KEXEC' in s390 ARCH. Removing
> the select won't impact anything. Test passed on a ibm-z system.

I apologize for my delay in responding, I did not have a computer with 
me during my holiday travel.

I was able to re-run my Kconfig test script with this patch series (now 
that I'm running this on private resources, it takes half a day 8( ). 
The script only performs comparisons of the .config before (LHSB) and 
after (RHSB) the patch series; it does NOT do any building. At any rate, 
what that revealed was only differences in s390. That means that all 
other arches do not have any unintended side effects. The differences 
with patch3 applied look like:

FAIL: allnoconfig arch/s390/configs/kasan.config
LHSB {'CONFIG_CRASH_CORE': 'y', 'CONFIG_KEXEC_CORE': 'y', 
'CONFIG_KEXEC': 'y'}
RHSB {'CONFIG_KEXEC': 'n'}

The 'allnoconfig' and 'olddefconfig' targets failed for all s390 
defconfigs. The LHSB is the pre-patch values, and the RHSB is the 
post-patch values. So this states that CRASH_CORE and KEXEC_CORE were 
set previously, but now they are not. KEXEC obviously is being turned 
off intentionally.

Hope this helps some.

Regards,

eric



> Baoquan He (3):
>    kernel/Kconfig.kexec: drop select of KEXEC for CRASH_DUMP
>    drivers/base/cpu: crash data showing should depends on KEXEC_CORE
>    s390/Kconfig: drop select of KEXEC
>
>   arch/arm/include/asm/kexec.h | 4 ----
>   arch/s390/Kconfig            | 1 -
>   drivers/base/cpu.c           | 6 +++---
>   kernel/Kconfig.kexec         | 1 -
>   4 files changed, 3 insertions(+), 9 deletions(-)
>

  parent reply	other threads:[~2023-11-26  0:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  7:36 [PATCH 0/3] kernel/Kconfig.kexec: drop select of KEXEC for CRASH_DUMP Baoquan He
2023-11-23  7:36 ` [PATCH 1/3] " Baoquan He
2023-11-23  8:23   ` Ignat Korchagin
2023-11-23 11:07     ` Baoquan He
2023-11-23  7:36 ` [PATCH 2/3] drivers/base/cpu: crash data showing should depends on KEXEC_CORE Baoquan He
2023-11-23  8:34   ` Ignat Korchagin
2023-11-23 11:15     ` Baoquan He
2023-11-24 16:44       ` Andrew Morton
2023-11-25  2:29         ` Baoquan He
2023-11-23 14:13   ` Alexander Gordeev
2023-11-23 14:27     ` Baoquan He
2023-11-23  7:36 ` [PATCH 3/3] s390/Kconfig: drop select of KEXEC Baoquan He
2023-11-23 13:43   ` Alexander Gordeev
2023-11-23 14:31     ` Baoquan He
2023-11-26  0:07 ` Eric DeVolder [this message]
2023-11-27  3:29   ` [PATCH 0/3] kernel/Kconfig.kexec: drop select of KEXEC for CRASH_DUMP 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=5ab45f48-9ec2-4611-81a2-4dc2f1854c4f@yahoo.com \
    --to=eric_devolder@yahoo.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=ignat@cloudflare.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.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