linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: kernel test robot <lkp@intel.com>, Pingfan Liu <piliu@redhat.com>,
	Nayna Jain <nayna@linux.ibm.com>,
	Kexec-ml <kexec@lists.infradead.org>,
	Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	Mimi Zohar <zohar@linux.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Sourabh Jain <sourabhjain@linux.ibm.com>,
	Petr Tesarik <ptesarik@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
	Eric Biederman <ebiederm@xmission.com>
Subject: Re: [PATCH v4 09/12] ppc64/kexec_file: setup backup region for kdump kernel
Date: Thu, 23 Jul 2020 21:28:55 -0300	[thread overview]
Message-ID: <874kpx69iw.fsf@morokweng.localdomain> (raw)
In-Reply-To: <159524964786.20855.15850644504721928289.stgit@hbathini.in.ibm.com>


Hari Bathini <hbathini@linux.ibm.com> writes:

> Though kdump kernel boots from loaded address, the first 64K bytes
> of it is copied down to real 0. So, setup a backup region to copy
> the first 64K bytes of crashed kernel, in purgatory, before booting
> into kdump kernel. Also, update reserve map with backup region and
> crashed kernel's memory to avoid kdump kernel from accidentially
> using that memory.
>
> Reported-by: kernel test robot <lkp@intel.com>
> [lkp: In v1, purgatory() declaration was missing]
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>

Reviewed-by: Thiago Jung Bauermann <bauerman@linux.ibm.com>

Just one minor comment below:

> @@ -1047,13 +1120,26 @@ int setup_new_fdt_ppc64(const struct kimage *image, void *fdt,
>  			goto out;
>  		}
>
> -		/* Ensure we don't touch crashed kernel's memory */
> -		ret = fdt_add_mem_rsv(fdt, 0, crashk_res.start);
> +		/*
> +		 * Ensure we don't touch crashed kernel's memory except the
> +		 * first 64K of RAM, which will be backed up.
> +		 */
> +		ret = fdt_add_mem_rsv(fdt, BACKUP_SRC_SIZE,

I know BACKUP_SRC_START is 0, but please forgive my pedantry when I say
that I think it's clearer if the start address above is changed to
BACKUP_SRC_START + BACKUP_SRC_SIZE...

> +				      crashk_res.start - BACKUP_SRC_SIZE);
>  		if (ret) {
>  			pr_err("Error reserving crash memory: %s\n",
>  			       fdt_strerror(ret));
>  			goto out;
>  		}
> +
> +		/* Ensure backup region is not used by kdump/capture kernel */
> +		ret = fdt_add_mem_rsv(fdt, image->arch.backup_start,
> +				      BACKUP_SRC_SIZE);
> +		if (ret) {
> +			pr_err("Error reserving memory for backup: %s\n",
> +			       fdt_strerror(ret));
> +			goto out;
> +		}
>  	}
>
>  out:

--
Thiago Jung Bauermann
IBM Linux Technology Center

  reply	other threads:[~2020-07-24  0:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 12:49 [PATCH v4 00/12] ppc64: enable kdump support for kexec_file_load syscall Hari Bathini
2020-07-20 12:50 ` [PATCH v4 01/12] kexec_file: allow archs to handle special regions while locating memory hole Hari Bathini
2020-07-20 12:50 ` [PATCH v4 02/12] powerpc/kexec_file: mark PPC64 specific code Hari Bathini
2020-07-20 12:51 ` [PATCH v4 03/12] powerpc/kexec_file: add helper functions for getting memory ranges Hari Bathini
2020-07-20 12:59   ` Hari Bathini
2020-07-23 22:12   ` Thiago Jung Bauermann
2020-07-20 12:52 ` [PATCH v4 04/12] ppc64/kexec_file: avoid stomping memory used by special regions Hari Bathini
2020-07-23 22:19   ` Thiago Jung Bauermann
2020-07-20 12:52 ` [PATCH v4 05/12] powerpc/drmem: make lmb walk a bit more flexible Hari Bathini
2020-07-20 12:52 ` [PATCH v4 06/12] ppc64/kexec_file: restrict memory usage of kdump kernel Hari Bathini
2020-07-24  0:06   ` Thiago Jung Bauermann
2020-07-24 14:08     ` Hari Bathini
2020-07-25  0:32       ` Thiago Jung Bauermann
2020-07-20 12:53 ` [PATCH v4 07/12] ppc64/kexec_file: add support to relocate purgatory Hari Bathini
2020-07-22  4:25   ` Michael Ellerman
2020-07-22 17:33     ` Hari Bathini
2020-07-23  6:47       ` Michael Ellerman
2020-07-20 12:53 ` [PATCH v4 08/12] ppc64/kexec_file: setup the stack for purgatory Hari Bathini
2020-07-20 12:54 ` [PATCH v4 09/12] ppc64/kexec_file: setup backup region for kdump kernel Hari Bathini
2020-07-24  0:28   ` Thiago Jung Bauermann [this message]
2020-07-20 12:54 ` [PATCH v4 10/12] ppc64/kexec_file: prepare elfcore header for crashing kernel Hari Bathini
2020-07-24  0:33   ` Thiago Jung Bauermann
2020-07-20 12:54 ` [PATCH v4 11/12] ppc64/kexec_file: add appropriate regions for memory reserve map Hari Bathini
2020-07-20 12:55 ` [PATCH v4 12/12] ppc64/kexec_file: fix kexec load failure with lack of memory hole Hari Bathini

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=874kpx69iw.fsf@morokweng.localdomain \
    --to=bauerman@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=hbathini@linux.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=lkp@intel.com \
    --cc=mahesh@linux.ibm.com \
    --cc=nayna@linux.ibm.com \
    --cc=piliu@redhat.com \
    --cc=ptesarik@suse.cz \
    --cc=sourabhjain@linux.ibm.com \
    --cc=vgoyal@redhat.com \
    --cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).