All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Klara Modin <klarasmodin@gmail.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	x86@kernel.org, linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
	linux-sh@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-riscv@lists.infradead.org, loongarch@lists.linux.dev,
	akpm@linux-foundation.org, ebiederm@xmission.com,
	hbathini@linux.ibm.com, piliu@redhat.com,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH linux-next v3 01/14] kexec: split crashkernel reservation code out from crash_core.c
Date: Mon, 29 Jan 2024 09:57:50 +0800	[thread overview]
Message-ID: <ZbcGHoLZfqro7i8g@MiWiFi-R3L-srv> (raw)
In-Reply-To: <0b14826b-9373-4458-919d-1da2a62d4226@gmail.com>

On 01/28/24 at 02:28am, Klara Modin wrote:
> Hi,
> 
> On 2024-01-24 06:12, Baoquan He wrote:
> > And also add config item CRASH_RESERVE to control its enabling of the
> > codes. And update config items which has relationship with crashkernel
> > reservation.
> > 
> > And also change ifdeffery from CONFIG_CRASH_CORE to CONFIG_CRASH_RESERVE
> > when those scopes are only crashkernel reservation related.
> 
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 502986237cb6..a9243e0948a3 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -2106,7 +2106,7 @@ config ARCH_SUPPORTS_CRASH_HOTPLUG
> >   	def_bool y
> >   config ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION
> > -	def_bool CRASH_CORE
> > +	def_bool CRASH_RESEERVE
> >   config PHYSICAL_START
> >   	hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
> 
> CRASH_RESEERVE is probably a typo and should be CRASH_RESERVE (with the
> former ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION isn't defined in my .config
> and `crashkernel=...` parameter has no effect).

You are right, thanks a lot. Will fix that.


WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Klara Modin <klarasmodin@gmail.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	x86@kernel.org, linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
	linux-sh@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-riscv@lists.infradead.org, loongarch@lists.linux.dev,
	akpm@linux-foundation.org, ebiederm@xmission.com,
	hbathini@linux.ibm.com, piliu@redhat.com,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH linux-next v3 01/14] kexec: split crashkernel reservation code out from crash_core.c
Date: Mon, 29 Jan 2024 09:57:50 +0800	[thread overview]
Message-ID: <ZbcGHoLZfqro7i8g@MiWiFi-R3L-srv> (raw)
In-Reply-To: <0b14826b-9373-4458-919d-1da2a62d4226@gmail.com>

On 01/28/24 at 02:28am, Klara Modin wrote:
> Hi,
> 
> On 2024-01-24 06:12, Baoquan He wrote:
> > And also add config item CRASH_RESERVE to control its enabling of the
> > codes. And update config items which has relationship with crashkernel
> > reservation.
> > 
> > And also change ifdeffery from CONFIG_CRASH_CORE to CONFIG_CRASH_RESERVE
> > when those scopes are only crashkernel reservation related.
> 
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 502986237cb6..a9243e0948a3 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -2106,7 +2106,7 @@ config ARCH_SUPPORTS_CRASH_HOTPLUG
> >   	def_bool y
> >   config ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION
> > -	def_bool CRASH_CORE
> > +	def_bool CRASH_RESEERVE
> >   config PHYSICAL_START
> >   	hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
> 
> CRASH_RESEERVE is probably a typo and should be CRASH_RESERVE (with the
> former ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION isn't defined in my .config
> and `crashkernel=...` parameter has no effect).

You are right, thanks a lot. Will fix that.


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

WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Klara Modin <klarasmodin@gmail.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	x86@kernel.org, linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
	linux-sh@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-riscv@lists.infradead.org, loongarch@lists.linux.dev,
	akpm@linux-foundation.org, ebiederm@xmission.com,
	hbathini@linux.ibm.com, piliu@redhat.com,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH linux-next v3 01/14] kexec: split crashkernel reservation code out from crash_core.c
Date: Mon, 29 Jan 2024 09:57:50 +0800	[thread overview]
Message-ID: <ZbcGHoLZfqro7i8g@MiWiFi-R3L-srv> (raw)
In-Reply-To: <0b14826b-9373-4458-919d-1da2a62d4226@gmail.com>

On 01/28/24 at 02:28am, Klara Modin wrote:
> Hi,
> 
> On 2024-01-24 06:12, Baoquan He wrote:
> > And also add config item CRASH_RESERVE to control its enabling of the
> > codes. And update config items which has relationship with crashkernel
> > reservation.
> > 
> > And also change ifdeffery from CONFIG_CRASH_CORE to CONFIG_CRASH_RESERVE
> > when those scopes are only crashkernel reservation related.
> 
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 502986237cb6..a9243e0948a3 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -2106,7 +2106,7 @@ config ARCH_SUPPORTS_CRASH_HOTPLUG
> >   	def_bool y
> >   config ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION
> > -	def_bool CRASH_CORE
> > +	def_bool CRASH_RESEERVE
> >   config PHYSICAL_START
> >   	hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
> 
> CRASH_RESEERVE is probably a typo and should be CRASH_RESERVE (with the
> former ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION isn't defined in my .config
> and `crashkernel=...` parameter has no effect).

You are right, thanks a lot. Will fix that.


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Klara Modin <klarasmodin@gmail.com>
Cc: linux-s390@vger.kernel.org, piliu@redhat.com,
	linux-sh@vger.kernel.org, x86@kernel.org,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-mips@vger.kernel.org, ebiederm@xmission.com,
	loongarch@lists.linux.dev, hbathini@linux.ibm.com,
	linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
	akpm@linux-foundation.org, linux-arm-kernel@lists.infradead.org,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH linux-next v3 01/14] kexec: split crashkernel reservation code out from crash_core.c
Date: Mon, 29 Jan 2024 09:57:50 +0800	[thread overview]
Message-ID: <ZbcGHoLZfqro7i8g@MiWiFi-R3L-srv> (raw)
In-Reply-To: <0b14826b-9373-4458-919d-1da2a62d4226@gmail.com>

On 01/28/24 at 02:28am, Klara Modin wrote:
> Hi,
> 
> On 2024-01-24 06:12, Baoquan He wrote:
> > And also add config item CRASH_RESERVE to control its enabling of the
> > codes. And update config items which has relationship with crashkernel
> > reservation.
> > 
> > And also change ifdeffery from CONFIG_CRASH_CORE to CONFIG_CRASH_RESERVE
> > when those scopes are only crashkernel reservation related.
> 
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 502986237cb6..a9243e0948a3 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -2106,7 +2106,7 @@ config ARCH_SUPPORTS_CRASH_HOTPLUG
> >   	def_bool y
> >   config ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION
> > -	def_bool CRASH_CORE
> > +	def_bool CRASH_RESEERVE
> >   config PHYSICAL_START
> >   	hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
> 
> CRASH_RESEERVE is probably a typo and should be CRASH_RESERVE (with the
> former ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION isn't defined in my .config
> and `crashkernel=...` parameter has no effect).

You are right, thanks a lot. Will fix that.


WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Klara Modin <klarasmodin@gmail.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	x86@kernel.org, linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
	linux-sh@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-riscv@lists.infradead.org, loongarch@lists.linux.dev,
	akpm@linux-foundation.org, ebiederm@xmission.com,
	hbathini@linux.ibm.com, piliu@redhat.com,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH linux-next v3 01/14] kexec: split crashkernel reservation code out from crash_core.c
Date: Mon, 29 Jan 2024 09:57:50 +0800	[thread overview]
Message-ID: <ZbcGHoLZfqro7i8g@MiWiFi-R3L-srv> (raw)
In-Reply-To: <0b14826b-9373-4458-919d-1da2a62d4226@gmail.com>

On 01/28/24 at 02:28am, Klara Modin wrote:
> Hi,
> 
> On 2024-01-24 06:12, Baoquan He wrote:
> > And also add config item CRASH_RESERVE to control its enabling of the
> > codes. And update config items which has relationship with crashkernel
> > reservation.
> > 
> > And also change ifdeffery from CONFIG_CRASH_CORE to CONFIG_CRASH_RESERVE
> > when those scopes are only crashkernel reservation related.
> 
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 502986237cb6..a9243e0948a3 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -2106,7 +2106,7 @@ config ARCH_SUPPORTS_CRASH_HOTPLUG
> >   	def_bool y
> >   config ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION
> > -	def_bool CRASH_CORE
> > +	def_bool CRASH_RESEERVE
> >   config PHYSICAL_START
> >   	hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
> 
> CRASH_RESEERVE is probably a typo and should be CRASH_RESERVE (with the
> former ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION isn't defined in my .config
> and `crashkernel=...` parameter has no effect).

You are right, thanks a lot. Will fix that.


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

  reply	other threads:[~2024-01-29  1:58 UTC|newest]

Thread overview: 140+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  5:12 [PATCH linux-next v3 00/14] Split crash out from kexec and clean up related config items Baoquan He
2024-01-24  5:12 ` Baoquan He
2024-01-24  5:12 ` Baoquan He
2024-01-24  5:12 ` Baoquan He
2024-01-24  5:12 ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 01/14] kexec: split crashkernel reservation code out from crash_core.c Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-28  1:28   ` Klara Modin
2024-01-28  1:28     ` Klara Modin
2024-01-28  1:28     ` Klara Modin
2024-01-28  1:28     ` Klara Modin
2024-01-28  1:28     ` Klara Modin
2024-01-29  1:57     ` Baoquan He [this message]
2024-01-29  1:57       ` Baoquan He
2024-01-29  1:57       ` Baoquan He
2024-01-29  1:57       ` Baoquan He
2024-01-29  1:57       ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 02/14] crash: split vmcoreinfo exporting " Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-03-25  8:24   ` Geert Uytterhoeven
2024-03-25  8:24     ` Geert Uytterhoeven
2024-03-25  8:24     ` Geert Uytterhoeven
2024-03-25  8:24     ` Geert Uytterhoeven
2024-03-25  8:24     ` Geert Uytterhoeven
2024-03-25  9:48     ` Baoquan He
2024-03-25  9:48       ` Baoquan He
2024-03-25  9:48       ` Baoquan He
2024-03-25  9:48       ` Baoquan He
2024-03-25  9:48       ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 03/14] crash: remove dependency of FA_DUMP on CRASH_DUMP Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 04/14] crash: split crash dumping code out from kexec_core.c Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 05/14] crash: clean up kdump related config items Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 06/14] x86, crash: wrap crash dumping code into crash related ifdefs Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24 23:02   ` Michael Kelley
2024-01-24 23:02     ` Michael Kelley
2024-01-24 23:02     ` Michael Kelley
2024-01-24 23:02     ` Michael Kelley
2024-01-24 23:02     ` Michael Kelley
2024-01-25  4:09     ` Baoquan He
2024-01-25  4:09       ` Baoquan He
2024-01-25  4:09       ` Baoquan He
2024-01-25  4:09       ` Baoquan He
2024-01-25  4:09       ` Baoquan He
2024-01-25  5:12       ` Michael Kelley
2024-01-25  5:12         ` Michael Kelley
2024-01-25  5:12         ` Michael Kelley
2024-01-25  5:12         ` Michael Kelley
2024-01-25  5:12         ` Michael Kelley
2024-01-25  9:17         ` Baoquan He
2024-01-25  9:17           ` Baoquan He
2024-01-25  9:17           ` Baoquan He
2024-01-25  9:17           ` Baoquan He
2024-01-25  9:17           ` Baoquan He
2024-01-25 15:30           ` Michael Kelley
2024-01-25 15:30             ` Michael Kelley
2024-01-25 15:30             ` Michael Kelley
2024-01-25 15:30             ` Michael Kelley
2024-01-25 15:30             ` Michael Kelley
2024-01-24  5:12 ` [PATCH linux-next v3 07/14] arm64, " Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 08/14] ppc, crash: enforce KEXEC and KEXEC_FILE to select CRASH_DUMP Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 09/14] s390, crash: wrap crash dumping code into crash related ifdefs Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 10/14] sh, " Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  8:13   ` John Paul Adrian Glaubitz
2024-01-24  8:13     ` John Paul Adrian Glaubitz
2024-01-24  8:13     ` John Paul Adrian Glaubitz
2024-01-24  8:13     ` John Paul Adrian Glaubitz
2024-01-24  8:13     ` John Paul Adrian Glaubitz
2024-01-24 14:38     ` Baoquan He
2024-01-24 14:38       ` Baoquan He
2024-01-24 14:38       ` Baoquan He
2024-01-24 14:38       ` Baoquan He
2024-01-24 14:38       ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 11/14] mips, " Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 12/14] riscv, " Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 13/14] arm, " Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12 ` [PATCH linux-next v3 14/14] loongarch, " Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-24  5:12   ` Baoquan He
2024-01-26  4:55 ` [PATCH linux-next v3 00/14] Split crash out from kexec and clean up related config items Nathan Chancellor
2024-01-26  4:55   ` Nathan Chancellor
2024-01-26  4:55   ` Nathan Chancellor
2024-01-26  4:55   ` Nathan Chancellor
2024-01-26  4:55   ` Nathan Chancellor
2024-01-26  6:07   ` Baoquan He
2024-01-26  6:07     ` Baoquan He
2024-01-26  6:07     ` Baoquan He
2024-01-26  6:07     ` Baoquan He
2024-01-26  6:07     ` 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=ZbcGHoLZfqro7i8g@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hbathini@linux.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=klarasmodin@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loongarch@lists.linux.dev \
    --cc=piliu@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    --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 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.