All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: kexec@lists.infradead.org
Subject: [RFC v2 3/6] crash hp: definitions and prototype changes
Date: Wed, 19 Jan 2022 16:25:44 +0800	[thread overview]
Message-ID: <20220119082544.GA18398@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220119082306.GA5158@MiWiFi-R3L-srv>

On 01/19/22 at 04:23pm, Baoquan He wrote:
> On 12/07/21 at 02:52pm, Eric DeVolder wrote:
> > This change adds members to struct kimage to facilitate crash
> > hotplug support.
> > 
> > This change also defines crash hotplug events and associated
> > prototypes.
> > 
> > Signed-off-by: Eric DeVolder <eric.devolder@oracle.com>
> > ---
> >  include/linux/kexec.h | 21 +++++++++++++++++++--
> >  1 file changed, 19 insertions(+), 2 deletions(-)
> > 
> > diff --git a/include/linux/kexec.h b/include/linux/kexec.h
> > index 0c994ae37729..068f853f1c65 100644
> > --- a/include/linux/kexec.h
> > +++ b/include/linux/kexec.h
> > @@ -221,8 +221,9 @@ struct crash_mem {
> >  extern int crash_exclude_mem_range(struct crash_mem *mem,
> >  				   unsigned long long mstart,
> >  				   unsigned long long mend);
> > -extern int crash_prepare_elf64_headers(struct crash_mem *mem, int kernel_map,
> > -				       void **addr, unsigned long *sz);
> > +extern int crash_prepare_elf64_headers(struct kimage *image,
> > +					struct crash_mem *mem, int kernel_map,
> > +					void **addr, unsigned long *sz);
> >  #endif /* CONFIG_KEXEC_FILE */
> >  
> >  #ifdef CONFIG_KEXEC_ELF
> > @@ -299,6 +300,13 @@ struct kimage {
> >  
> >  	/* Information for loading purgatory */
> >  	struct purgatory_info purgatory_info;
> > +
> > +#ifdef CONFIG_CRASH_HOTPLUG
> > +	bool hotplug_event;
> > +	int offlinecpu;
> > +	bool elf_index_valid;
> > +	int elf_index;
> 
> Do we really need elf_index_valid? Can we initialize elf_index to , e.g '-1',
> then check if the value is valid?

Sorry, please ignore this one, I will add this comment in v3 thread.

> 
> > +#endif
> >  #endif
> >  
> >  #ifdef CONFIG_IMA_KEXEC
> > @@ -315,6 +323,15 @@ struct kimage {
> >  	unsigned long elf_load_addr;
> >  };
> >  
> > +#ifdef CONFIG_CRASH_HOTPLUG
> > +void arch_crash_hotplug_handler(struct kimage *image,
> > +	unsigned int hp_action, unsigned long a, unsigned long b);
> > +#define KEXEC_CRASH_HP_REMOVE_CPU   0
> > +#define KEXEC_CRASH_HP_ADD_CPU      1
> > +#define KEXEC_CRASH_HP_REMOVE_MEMORY 2
> > +#define KEXEC_CRASH_HP_ADD_MEMORY   3
> > +#endif /* CONFIG_CRASH_HOTPLUG */
> > +
> >  /* kexec interface functions */
> >  extern void machine_kexec(struct kimage *image);
> >  extern int machine_kexec_prepare(struct kimage *image);
> > -- 
> > 2.27.0
> > 
> 



WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Eric DeVolder <eric.devolder@oracle.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	kexec@lists.infradead.org, ebiederm@xmission.com,
	dyoung@redhat.com, vgoyal@redhat.com, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	hpa@zytor.com, nramas@linux.microsoft.com,
	thomas.lendacky@amd.com, robh@kernel.org, efault@gmx.de,
	rppt@kernel.org, konrad.wilk@oracle.com,
	boris.ostrovsky@oracle.com
Subject: Re: [RFC v2 3/6] crash hp: definitions and prototype changes
Date: Wed, 19 Jan 2022 16:25:44 +0800	[thread overview]
Message-ID: <20220119082544.GA18398@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220119082306.GA5158@MiWiFi-R3L-srv>

On 01/19/22 at 04:23pm, Baoquan He wrote:
> On 12/07/21 at 02:52pm, Eric DeVolder wrote:
> > This change adds members to struct kimage to facilitate crash
> > hotplug support.
> > 
> > This change also defines crash hotplug events and associated
> > prototypes.
> > 
> > Signed-off-by: Eric DeVolder <eric.devolder@oracle.com>
> > ---
> >  include/linux/kexec.h | 21 +++++++++++++++++++--
> >  1 file changed, 19 insertions(+), 2 deletions(-)
> > 
> > diff --git a/include/linux/kexec.h b/include/linux/kexec.h
> > index 0c994ae37729..068f853f1c65 100644
> > --- a/include/linux/kexec.h
> > +++ b/include/linux/kexec.h
> > @@ -221,8 +221,9 @@ struct crash_mem {
> >  extern int crash_exclude_mem_range(struct crash_mem *mem,
> >  				   unsigned long long mstart,
> >  				   unsigned long long mend);
> > -extern int crash_prepare_elf64_headers(struct crash_mem *mem, int kernel_map,
> > -				       void **addr, unsigned long *sz);
> > +extern int crash_prepare_elf64_headers(struct kimage *image,
> > +					struct crash_mem *mem, int kernel_map,
> > +					void **addr, unsigned long *sz);
> >  #endif /* CONFIG_KEXEC_FILE */
> >  
> >  #ifdef CONFIG_KEXEC_ELF
> > @@ -299,6 +300,13 @@ struct kimage {
> >  
> >  	/* Information for loading purgatory */
> >  	struct purgatory_info purgatory_info;
> > +
> > +#ifdef CONFIG_CRASH_HOTPLUG
> > +	bool hotplug_event;
> > +	int offlinecpu;
> > +	bool elf_index_valid;
> > +	int elf_index;
> 
> Do we really need elf_index_valid? Can we initialize elf_index to , e.g '-1',
> then check if the value is valid?

Sorry, please ignore this one, I will add this comment in v3 thread.

> 
> > +#endif
> >  #endif
> >  
> >  #ifdef CONFIG_IMA_KEXEC
> > @@ -315,6 +323,15 @@ struct kimage {
> >  	unsigned long elf_load_addr;
> >  };
> >  
> > +#ifdef CONFIG_CRASH_HOTPLUG
> > +void arch_crash_hotplug_handler(struct kimage *image,
> > +	unsigned int hp_action, unsigned long a, unsigned long b);
> > +#define KEXEC_CRASH_HP_REMOVE_CPU   0
> > +#define KEXEC_CRASH_HP_ADD_CPU      1
> > +#define KEXEC_CRASH_HP_REMOVE_MEMORY 2
> > +#define KEXEC_CRASH_HP_ADD_MEMORY   3
> > +#endif /* CONFIG_CRASH_HOTPLUG */
> > +
> >  /* kexec interface functions */
> >  extern void machine_kexec(struct kimage *image);
> >  extern int machine_kexec_prepare(struct kimage *image);
> > -- 
> > 2.27.0
> > 
> 


  reply	other threads:[~2022-01-19  8:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 19:51 [RFC v2 0/6] crash: Kernel handling of CPU and memory hot un/plug Eric DeVolder
2021-12-07 19:51 ` Eric DeVolder
2021-12-07 19:51 ` [RFC v2 1/6] crash: fix minor typo/bug in debug message Eric DeVolder
2021-12-07 19:51   ` Eric DeVolder
2021-12-07 19:52 ` [RFC v2 2/6] crash hp: Introduce CRASH_HOTPLUG configuration options Eric DeVolder
2021-12-07 19:52   ` Eric DeVolder
2021-12-07 19:52 ` [RFC v2 3/6] crash hp: definitions and prototype changes Eric DeVolder
2021-12-07 19:52   ` Eric DeVolder
2022-01-19  8:23   ` Baoquan He
2022-01-19  8:23     ` Baoquan He
2022-01-19  8:25     ` Baoquan He [this message]
2022-01-19  8:25       ` Baoquan He
2021-12-07 19:52 ` [RFC v2 4/6] crash hp: generic crash hotplug support infrastructure Eric DeVolder
2021-12-07 19:52   ` Eric DeVolder
2021-12-08 13:38   ` David Hildenbrand
2021-12-08 13:38     ` David Hildenbrand
2021-12-09 15:40     ` Eric DeVolder
2021-12-09 15:40       ` Eric DeVolder
2021-12-07 19:52 ` [RFC v2 5/6] crash hp: kexec_file changes for crash hotplug support Eric DeVolder
2021-12-07 19:52   ` Eric DeVolder
2021-12-07 19:52 ` [RFC v2 6/6] crash hp: Add x86 " Eric DeVolder
2021-12-07 19:52   ` Eric DeVolder
2022-01-05 14:25 ` [RFC v2 0/6] crash: Kernel handling of CPU and memory hot un/plug Eric DeVolder
2022-01-05 14:25   ` Eric DeVolder
2022-01-10  8:04   ` Baoquan He
2022-01-10  8:04     ` Baoquan He
2022-01-10 19:59     ` Eric DeVolder
2022-01-10 19:59       ` Eric DeVolder

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=20220119082544.GA18398@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=kexec@lists.infradead.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.