All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pingfan Liu <piliu@redhat.com>,
	Kexec-ml <kexec@lists.infradead.org>,
	Mimi Zohar <zohar@linux.ibm.com>,
	Nayna Jain <nayna@linux.ibm.com>, Petr Tesarik <ptesarik@suse.cz>,
	Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	Sourabh Jain <sourabhjain@linux.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Eric Biederman <ebiederm@xmission.com>,
	Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH v4 03/12] powerpc/kexec_file: add helper functions for getting memory ranges
Date: Thu, 23 Jul 2020 19:12:05 -0300	[thread overview]
Message-ID: <878sf96fuy.fsf@morokweng.localdomain> (raw)
In-Reply-To: <159524946347.20855.15784642736087777919.stgit@hbathini.in.ibm.com>


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

> In kexec case, the kernel to be loaded uses the same memory layout as
> the running kernel. So, passing on the DT of the running kernel would
> be good enough.
>
> But in case of kdump, different memory ranges are needed to manage
> loading the kdump kernel, booting into it and exporting the elfcore
> of the crashing kernel. The ranges are exclude memory ranges, usable
> memory ranges, reserved memory ranges and crash memory ranges.
>
> Exclude memory ranges specify the list of memory ranges to avoid while
> loading kdump segments. Usable memory ranges list the memory ranges
> that could be used for booting kdump kernel. Reserved memory ranges
> list the memory regions for the loading kernel's reserve map. Crash
> memory ranges list the memory ranges to be exported as the crashing
> kernel's elfcore.
>
> Add helper functions for setting up the above mentioned memory ranges.
> This helpers facilitate in understanding the subsequent changes better
> and make it easy to setup the different memory ranges listed above, as
> and when appropriate.
>
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
> Tested-by: Pingfan Liu <piliu@redhat.com>

Just one comment below, but regardless:

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

> +/**
> + * add_htab_mem_range - Adds htab range to the given memory ranges list,
> + *                      if it exists
> + * @mem_ranges:         Range list to add the memory range to.
> + *
> + * Returns 0 on success, negative errno on error.
> + */
> +int add_htab_mem_range(struct crash_mem **mem_ranges)
> +{
> +	if (!htab_address)
> +		return 0;
> +
> +	return add_mem_range(mem_ranges, __pa(htab_address), htab_size_bytes);
> +}

I believe you need to surround this function with `#ifdef
CONFIG_PPC_BOOK3S_64` and `#endif` to match what is done in
<asm/kexec_ranges.h>.

--
Thiago Jung Bauermann
IBM Linux Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: 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 03/12] powerpc/kexec_file: add helper functions for getting memory ranges
Date: Thu, 23 Jul 2020 19:12:05 -0300	[thread overview]
Message-ID: <878sf96fuy.fsf@morokweng.localdomain> (raw)
In-Reply-To: <159524946347.20855.15784642736087777919.stgit@hbathini.in.ibm.com>


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

> In kexec case, the kernel to be loaded uses the same memory layout as
> the running kernel. So, passing on the DT of the running kernel would
> be good enough.
>
> But in case of kdump, different memory ranges are needed to manage
> loading the kdump kernel, booting into it and exporting the elfcore
> of the crashing kernel. The ranges are exclude memory ranges, usable
> memory ranges, reserved memory ranges and crash memory ranges.
>
> Exclude memory ranges specify the list of memory ranges to avoid while
> loading kdump segments. Usable memory ranges list the memory ranges
> that could be used for booting kdump kernel. Reserved memory ranges
> list the memory regions for the loading kernel's reserve map. Crash
> memory ranges list the memory ranges to be exported as the crashing
> kernel's elfcore.
>
> Add helper functions for setting up the above mentioned memory ranges.
> This helpers facilitate in understanding the subsequent changes better
> and make it easy to setup the different memory ranges listed above, as
> and when appropriate.
>
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
> Tested-by: Pingfan Liu <piliu@redhat.com>

Just one comment below, but regardless:

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

> +/**
> + * add_htab_mem_range - Adds htab range to the given memory ranges list,
> + *                      if it exists
> + * @mem_ranges:         Range list to add the memory range to.
> + *
> + * Returns 0 on success, negative errno on error.
> + */
> +int add_htab_mem_range(struct crash_mem **mem_ranges)
> +{
> +	if (!htab_address)
> +		return 0;
> +
> +	return add_mem_range(mem_ranges, __pa(htab_address), htab_size_bytes);
> +}

I believe you need to surround this function with `#ifdef
CONFIG_PPC_BOOK3S_64` and `#endif` to match what is done in
<asm/kexec_ranges.h>.

--
Thiago Jung Bauermann
IBM Linux Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: Pingfan Liu <piliu@redhat.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	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 03/12] powerpc/kexec_file: add helper functions for getting memory ranges
Date: Thu, 23 Jul 2020 19:12:05 -0300	[thread overview]
Message-ID: <878sf96fuy.fsf@morokweng.localdomain> (raw)
In-Reply-To: <159524946347.20855.15784642736087777919.stgit@hbathini.in.ibm.com>


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

> In kexec case, the kernel to be loaded uses the same memory layout as
> the running kernel. So, passing on the DT of the running kernel would
> be good enough.
>
> But in case of kdump, different memory ranges are needed to manage
> loading the kdump kernel, booting into it and exporting the elfcore
> of the crashing kernel. The ranges are exclude memory ranges, usable
> memory ranges, reserved memory ranges and crash memory ranges.
>
> Exclude memory ranges specify the list of memory ranges to avoid while
> loading kdump segments. Usable memory ranges list the memory ranges
> that could be used for booting kdump kernel. Reserved memory ranges
> list the memory regions for the loading kernel's reserve map. Crash
> memory ranges list the memory ranges to be exported as the crashing
> kernel's elfcore.
>
> Add helper functions for setting up the above mentioned memory ranges.
> This helpers facilitate in understanding the subsequent changes better
> and make it easy to setup the different memory ranges listed above, as
> and when appropriate.
>
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
> Tested-by: Pingfan Liu <piliu@redhat.com>

Just one comment below, but regardless:

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

> +/**
> + * add_htab_mem_range - Adds htab range to the given memory ranges list,
> + *                      if it exists
> + * @mem_ranges:         Range list to add the memory range to.
> + *
> + * Returns 0 on success, negative errno on error.
> + */
> +int add_htab_mem_range(struct crash_mem **mem_ranges)
> +{
> +	if (!htab_address)
> +		return 0;
> +
> +	return add_mem_range(mem_ranges, __pa(htab_address), htab_size_bytes);
> +}

I believe you need to surround this function with `#ifdef
CONFIG_PPC_BOOK3S_64` and `#endif` to match what is done in
<asm/kexec_ranges.h>.

--
Thiago Jung Bauermann
IBM Linux Technology Center

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

  parent reply	other threads:[~2020-07-23 22:12 UTC|newest]

Thread overview: 72+ 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:49 ` Hari Bathini
2020-07-20 12:49 ` 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   ` Hari Bathini
2020-07-20 12:50   ` Hari Bathini
2020-07-20 12:50 ` [PATCH v4 02/12] powerpc/kexec_file: mark PPC64 specific code Hari Bathini
2020-07-20 12:50   ` Hari Bathini
2020-07-20 12:50   ` 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:51   ` Hari Bathini
2020-07-20 12:51   ` Hari Bathini
2020-07-20 12:59   ` Hari Bathini
2020-07-20 12:59     ` Hari Bathini
2020-07-20 12:59     ` Hari Bathini
2020-07-23 22:12   ` Thiago Jung Bauermann [this message]
2020-07-23 22:12     ` Thiago Jung Bauermann
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-20 12:52   ` Hari Bathini
2020-07-20 12:52   ` Hari Bathini
2020-07-23 22:19   ` Thiago Jung Bauermann
2020-07-23 22:19     ` Thiago Jung Bauermann
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   ` Hari Bathini
2020-07-20 12:52   ` Hari Bathini
2020-07-20 12:52 ` [PATCH v4 06/12] ppc64/kexec_file: restrict memory usage of kdump kernel Hari Bathini
2020-07-20 12:52   ` Hari Bathini
2020-07-20 12:52   ` Hari Bathini
2020-07-24  0:06   ` Thiago Jung Bauermann
2020-07-24  0:06     ` Thiago Jung Bauermann
2020-07-24  0:06     ` Thiago Jung Bauermann
2020-07-24 14:08     ` Hari Bathini
2020-07-24 14:08       ` Hari Bathini
2020-07-24 14:08       ` Hari Bathini
2020-07-25  0:32       ` Thiago Jung Bauermann
2020-07-25  0:32         ` Thiago Jung Bauermann
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-20 12:53   ` Hari Bathini
2020-07-20 12:53   ` Hari Bathini
2020-07-22  4:25   ` Michael Ellerman
2020-07-22  4:25     ` Michael Ellerman
2020-07-22  4:25     ` Michael Ellerman
2020-07-22 17:33     ` Hari Bathini
2020-07-22 17:33       ` Hari Bathini
2020-07-22 17:33       ` Hari Bathini
2020-07-23  6:47       ` Michael Ellerman
2020-07-23  6:47         ` Michael Ellerman
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:53   ` Hari Bathini
2020-07-20 12:53   ` Hari Bathini
2020-07-20 12:54 ` [PATCH v4 09/12] ppc64/kexec_file: setup backup region for kdump kernel Hari Bathini
2020-07-20 12:54   ` Hari Bathini
2020-07-20 12:54   ` Hari Bathini
2020-07-24  0:28   ` Thiago Jung Bauermann
2020-07-24  0:28     ` Thiago Jung Bauermann
2020-07-24  0:28     ` Thiago Jung Bauermann
2020-07-20 12:54 ` [PATCH v4 10/12] ppc64/kexec_file: prepare elfcore header for crashing kernel Hari Bathini
2020-07-20 12:54   ` Hari Bathini
2020-07-20 12:54   ` Hari Bathini
2020-07-24  0:33   ` Thiago Jung Bauermann
2020-07-24  0:33     ` Thiago Jung Bauermann
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:54   ` Hari Bathini
2020-07-20 12:54   ` 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
2020-07-20 12:55   ` Hari Bathini
2020-07-20 12:55   ` 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=878sf96fuy.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=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --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 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.