. Elaborated on why exceptions should not be changed to big endian during
fadump boot.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/fadump.h | 52 ---
arch/powerpc/kernel/fadump.c | 114 +
arch/powerpc
for
filtering the kernel dump. Tested this changes successfully with makedumpfile
tool that supports vmemmap to physical address translation outside zone normal.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/pgalloc-64.h |4
arch/powerpc/kernel
and removed #ifdef around extern.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/pgalloc-64.h |2 ++
arch/powerpc/kernel/machine_kexec.c | 12
2 files changed, 14 insertions(+)
diff --git a/arch/powerpc/include/asm/pgalloc-64.h
b/arch/powerpc
the patches successfully on both pseries and powernv
platforms.
---
Hari Bathini (2):
pstore: Add pstore type id for firmware partition
pstore: add pstore support on powernv
arch/powerpc/include/asm/nvram.h| 50 ++
arch/powerpc/include/asm/rtas.h |2
This patch adds a pstore type id to be used for opal specific
nvram partitions.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
fs/pstore/inode.c |3 +++
include/linux/pstore.h |1 +
2 files changed, 4 insertions(+)
diff --git a/fs/pstore/inode.c b/fs/pstore/inode.c
, moves common code for pseries and powernv to
arch/powerpc/kernel/nvram_64.c file.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/nvram.h| 50 ++
arch/powerpc/include/asm/rtas.h |2
arch/powerpc/kernel/nvram_64.c
On 12/04/2014 11:07 AM, Michael Ellerman wrote:
On Wed, 2014-03-12 at 11:03:15 UTC, Hari Bathini wrote:
This patch extends pstore, a generic interface to platform dependent
persistent storage, support for powernv platform to capture certain
useful information, during dying moments
can conveniently ignore
resetting endianess as crashkernel is always of same endianess as primary
kernel.
This patch adds a new inline function to say if this is kdump path. This
function
is used at places where such a check is needed.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
the patches successfully on both pseries and powernv
platforms.
---
Hari Bathini (3):
powerpc/nvram: move generic code for nvram and pstore
pstore: Add pstore type id for firmware partition
pstore: add pstore support on powernv
arch/powerpc/include/asm/nvram.h| 50
With minor checks, we can move most of the code for nvram
under pseries to a common place to be re-used by other
powerpc platforms like powernv. This patch moves such
common code to arch/powerpc/kernel/nvram_64.c file.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc
This patch adds a pstore type id to be used for opal specific
nvram partitions.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
fs/pstore/inode.c |3 +++
include/linux/pstore.h |1 +
2 files changed, 4 insertions(+)
diff --git a/fs/pstore/inode.c b/fs/pstore/inode.c
This patch extends pstore, a generic interface to platform dependent
persistent storage, support for powernv platform to capture certain
useful information, during dying moments. Such support is already in
place for pseries platform. This patch re-uses most of that code.
Signed-off-by: Hari
On 12/17/2014 05:33 AM, Michael Ellerman wrote:
On Tue, 2014-12-16 at 23:35 +0530, Hari Bathini wrote:
With minor checks, we can move most of the code for nvram
under pseries to a common place to be re-used by other
powerpc platforms like powernv. This patch moves such
common code to arch
v1:
Instead of skipping, ignore failure in enabling big endian exception
during crash
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/kexec.h | 10 ++
arch/powerpc/kernel/machine_kexec_64.c |2 +-
arch/powerpc/platforms/pseries/lpar.c | 10
the patches successfully on both pseries and powernv
platforms.
Changes from v2:
Added an empty version of clobbering_unread_rtas_event()
routine for !PSERIES, to avoid ifdef at the call sites
---
Hari Bathini (3):
powerpc/nvram: move generic code for nvram and pstore
pstore: Add
With minor checks, we can move most of the code for nvram
under pseries to a common place to be re-used by other
powerpc platforms like powernv. This patch moves such
common code to arch/powerpc/kernel/nvram_64.c file.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc
This patch adds a pstore type id to be used for opal specific
nvram partitions.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
fs/pstore/inode.c |3 +++
include/linux/pstore.h |1 +
2 files changed, 4 insertions(+)
diff --git a/fs/pstore/inode.c b/fs/pstore/inode.c
This patch extends pstore, a generic interface to platform dependent
persistent storage, support for powernv platform to capture certain
useful information, during dying moments. Such support is already in
place for pseries platform. This patch re-uses most of that code.
Signed-off-by: Hari
This patch adds a new PPC64 partition type to be used for opal
specific nvram partition. A new partition type is needed as none
of the existing type matches this partition type.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
Cc: Anton Vorontsov an...@enomsg.org
Cc: Colin Cross ccr
CONFIG_PPC_PSERIES or CONFIG_PPC_POWERNV
flag is used in this patchset, it is to reduce the kernel size in cases
where this flag is not set and doesn't have any impact logic wise.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
Cc: Anton Vorontsov an...@enomsg.org
Cc: Colin Cross ccr...@android.com
Cc
With minor checks, we can move most of the code for nvram
under pseries to a common place to be re-used by other
powerpc platforms like powernv. This patch moves such
common code to arch/powerpc/kernel/nvram_64.c file.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc
the patches successfully on both pseries and powernv
platforms. Also, tested the patches successfully, on a kernel
compiled with both CONFIG_PPC_PSERIES=y CONFIG_PPC_POWERNV=y.
Changes from v3:
1. Updated the changelog
2. Resolved compile issues with !CONFIG_PPC_PSERIES
---
Hari Bathini (3
On 01/14/2015 10:01 AM, Michael Ellerman wrote:
On Wed, 2014-12-24 at 17:28 +0530, Hari Bathini wrote:
With minor checks, we can move most of the code for nvram
under pseries to a common place to be re-used by other
powerpc platforms like powernv. This patch moves such
common code to arch
On 01/15/2015 03:58 AM, Michael Ellerman wrote:
On Wed, 2015-01-14 at 23:35 +0530, Hari Bathini wrote:
On 01/14/2015 10:01 AM, Michael Ellerman wrote:
On Wed, 2014-12-24 at 17:28 +0530, Hari Bathini wrote:
With minor checks, we can move most of the code for nvram
under pseries to a common
On 01/30/2015 10:12 PM, Arnd Bergmann wrote:
On Friday 30 January 2015 20:44:00 Hari Bathini wrote:
With minor checks, we can move most of the code for nvram
under pseries to a common place to be re-used by other
powerpc platforms like powernv. This patch moves such
common code to arch/powerpc
This patch adds a new PPC64 partition type to be used for opal
specific nvram partition. A new partition type is needed as none
of the existing type matches this partition type.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
fs/pstore/inode.c |3 +++
include/linux/pstore.h
While we are here, let us make timestamp related code
y2038-safe.
Suggested-by: Arnd Bergmann a...@arndb.de
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/rtas.h|3 ++-
arch/powerpc/kernel/nvram_64.c |6 +++---
arch/powerpc/platforms
the patches successfully on both pseries and powernv
platforms. Also, tested the patches successfully, on a kernel
compiled with both CONFIG_PPC_PSERIES=y CONFIG_PPC_POWERNV=y.
Changes from v4:
1. Added a patch for y2038-safe code changes
---
Hari Bathini (4):
powerpc/nvram: move generic
With minor checks, we can move most of the code for nvram
under pseries to a common place to be re-used by other
powerpc platforms like powernv. This patch moves such
common code to arch/powerpc/kernel/nvram_64.c file.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc
CONFIG_PPC_PSERIES or CONFIG_PPC_POWERNV
flag is used in this patchset, it is to reduce the kernel size in cases
where this flag is not set and doesn't have any impact logic wise.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/kernel/nvram_64.c | 25
On 02/06/2015 01:06 AM, Hari Bathini wrote:
This patch adds a new PPC64 partition type to be used for opal
specific nvram partition. A new partition type is needed as none
of the existing type matches this partition type.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
This patch
removes the error message in case pstore.backend != nvram.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/kernel/nvram_64.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/nvram_64.c b/arch/powerpc/kernel/nvram_64.c
index
On 11/05/2015 07:02 AM, David Gibson wrote:
On Wed, 4 Nov 2015 14:54:51 +0100
Laurent Vivier <lviv...@redhat.com> wrote:
On 04/11/2015 13:34, Hari Bathini wrote:
On 10/16/2015 12:30 AM, Laurent Vivier wrote:
On kexec, all secondary offline CPUs are onlined before
starting the new
On 10/16/2015 12:30 AM, Laurent Vivier wrote:
On kexec, all secondary offline CPUs are onlined before
starting the new kernel, this is not done in the case of kdump.
If kdump is configured and a kernel crash occurs whereas
some secondaries CPUs are offline (SMT=off),
the new kernel is not able
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Reviewed-by: Mahesh J Salgaonkar <mah...@linux.vnet.ibm.com>
---
Changes in v2:
1. Changed subject from "[PATCH v2 2/2] powerpc/fadump: add support to parse
size based on memory r
to reserve
memory for fadump based on system memory size.
---
Hari Bathini (2):
refactor code parsing size based on memory range
powerpc/fadump: parse fadump reserve memory size based on memory range
arch/powerpc/kernel/fadump.c | 64
include/linux/kernel.h
.
Cc: Eric Biederman <ebied...@xmission.com>
Cc: Vivek Goyal <vgo...@redhat.com>
Cc: Rusty Russell <ru...@rustcorp.com.au>
Cc: ke...@lists.infradead.org
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
changes in v2:
1. Rebased to latest upstream.
2. Mark
On 06/24/2016 10:56 AM, Michael Ellerman wrote:
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote:
Currently, crashkernel parameter supports the below syntax to parse size
based on memory range:
crashkernel=:[,:,...]
While such parsing is implemented for crashkernel parameter
On 03/30/2016 04:47 PM, Michael Ellerman wrote:
On Wed, 2016-03-30 at 13:14 +0530, Hari Bathini wrote:
Alternatively, how about moving the OOLs handlers that can't be branched with
LOAD_HANDLER under __end_interrupts. This way we won't be copying more than a
few absolutely needed handlers
/production kernel and kdump kernel.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Signed-off-by: Mahesh Salgaonkar <mah...@linux.vnet.ibm.com>
---
changes from v2:
2. Move the OOL handlers before __end_interrupts marker instead of moving the
__end_interrupts mar
as a comment but could be misleading at times if
it isn't in sync with the code, as is the case now. So, let us avoid
this confusion by having a better comment and removing __end_handlers
marker altogether.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/kernel/exce
iled
I tested this patch successfully on ppc64, ppc64le lpars and baremetal
environments. Couldn't test it on IBM cell blade though but expecting no
problems with this patch in IBM cell blade environment as well. If
someone can test this patch in cell platform, it would be great.
Signed-off-by:
/production kernel and kdump kernel.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Signed-off-by: Mahesh Salgaonkar <mah...@linux.vnet.ibm.com>
---
Michael, I did test this patchset in different scenarios. But if you feel
the change is too radical, we could go with ver
On 04/01/2016 04:07 PM, Michael Ellerman wrote:
On Fri, 2016-04-01 at 12:23 +0530, Hari Bathini wrote:
On 04/01/2016 11:44 AM, Michael Ellerman wrote:
On Wed, 2016-03-30 at 23:49 +0530, Hari Bathini wrote:
Some of the interrupt vectors on 64-bit POWER server processors are
only 32 bytes
On 03/29/2016 03:47 PM, Michael Ellerman wrote:
Hi Hari,
You win the "Best Change Log of the Year" award.
Some comments below ...
On Mon, 2016-28-03 at 11:23:22 UTC, Hari Bathini wrote:
Some of the interrupt vectors on 64-bit POWER server processors are
only 32 bytes long (8 in
On 03/30/2016 12:44 PM, Hari Bathini wrote:
On 03/30/2016 05:55 AM, Michael Ellerman wrote:
On Tue, 2016-29-03 at 18:34:37 UTC, Hari Bathini wrote:
diff --git a/arch/powerpc/kernel/exceptions-64s.S
b/arch/powerpc/kernel/exceptions-64s.S
index 7716ceb..e598580 100644
--- a/arch/powerpc
successfully in kdump scenario, on a lpar with 4K page
size by using different default/production kernel and kdump kernel.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Signed-off-by: Mahesh Salgaonkar <mah...@linux.vnet.ibm.com>
---
changes from v1:
1. Changed the subjec
On 04/01/2016 11:44 AM, Michael Ellerman wrote:
On Wed, 2016-03-30 at 23:49 +0530, Hari Bathini wrote:
Some of the interrupt vectors on 64-bit POWER server processors are
only 32 bytes long (8 instructions), which is not enough for the full
...
Let us fix this undependable code path
, considering the relocation on
exception feature that allows exceptions to be raised in virtual mode (IR=DR=1).
This fix has been tested successfully in kdump scenario, on a lpar with 4K page
size by using different default/production kernel and kdump kernel.
Signed-off-by: Hari Bathini <hb
On 03/30/2016 05:55 AM, Michael Ellerman wrote:
On Tue, 2016-29-03 at 18:34:37 UTC, Hari Bathini wrote:
diff --git a/arch/powerpc/kernel/exceptions-64s.S
b/arch/powerpc/kernel/exceptions-64s.S
index 7716ceb..e598580 100644
--- a/arch/powerpc/kernel/exceptions-64s.S
+++ b/arch/powerpc/kernel
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v1:
1. Changed subject from "powerpc/fadump: add support to specify memory range
based size"
2. Reused crashkernel parsing code that was moved to kernel/params.c
.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
While this patch in itself has nothing to do with powerpc,
the powerpc patch (2/2) depends on this patch..
include/linux/kernel.h |5 +++
kernel/kexec_core.c| 63 +++-
kernel/pa
using the same commandline parameter for different system
memory sizes.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/kernel/fadump.c | 127 +++---
1 file changed, 118 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/
-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/include/asm/fadump.h |6 ++
arch/powerpc/kernel/fadump.c |4
2 files changed, 10 insertions(+)
diff --git a/arch/powerpc/include/asm/fadump.h
b/arch/powerpc/include/asm/fadump.h
index b4407d0..2
mah...@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/kernel/fadump.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadump.c
index a7fef3e..c75783c 100644
--- a/
On 04/15/2016 06:29 PM, Michael Ellerman wrote:
On Fri, 2016-04-15 at 21:06 +1000, Michael Ellerman wrote:
Hi Hari,
Thanks for persisting with this.
On Thu, 2016-07-04 at 21:58:50 UTC, Hari Bathini wrote:
With the previous patch, we choke out whatever little space is left
below 0x7000
On 05/07/2016 09:42 AM, Michael Ellerman wrote:
On Fri, 2016-06-05 at 11:51:08 UTC, Hari Bathini wrote:
Kernel parameter 'nr_cpus' can be used to limit the maximum number
of processors that an SMP kernel could support. This patch extends
this to fadump by introducing 'fadump_nr_cpus
On 05/07/2016 09:41 AM, Michael Ellerman wrote:
On Fri, 2016-06-05 at 11:50:37 UTC, Hari Bathini wrote:
Currently, memory for fadump can be specified with fadump_reserve_mem=size,
where only a fixed size can be specified. This patch tries to extend this
syntax to support conditional
in parsing the crashkernel
parameter.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v1:
1. Updated changelog
include/linux/kernel.h |5 +++
kernel/kexec_core.c| 63 +++-
kernel/params.c
to reserve
memory for fadump based on system memory size.
---
Hari Bathini (2):
kexec: refactor code parsing size based on memory range
powerpc/fadump: parse fadump reserve memory size based on memory range
arch/powerpc/kernel/fadump.c | 64
include/linux
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Reviewed-by: Mahesh J Salgaonkar <mah...@linux.vnet.ibm.com>
---
arch/powerpc/kernel/fadump.c | 64 --
1 file changed, 55 insertions(+),
in parsing the crashkernel
parameter.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v2:
1. Moved the code to lib/cmdline.c instead of kernel/params.c
include/linux/kernel.h |5 ++
kernel/kexec_core.c| 63 ++---
lib/cmdline.c
to reserve
memory for fadump based on system memory size.
---
Hari Bathini (2):
kexec: refactor code parsing size based on memory range
powerpc/fadump: parse fadump reserve memory size based on memory range
arch/powerpc/kernel/fadump.c | 63 ++---
include/linux/kernel.h
s.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Reviewed-by: Mahesh J Salgaonkar <mah...@linux.vnet.ibm.com>
---
Changes from v2:
1. Updated changelog
arch/powerpc/kernel/fadump.c | 63 --
1 file changed, 54 insertions(+), 9 de
Ping..
On Friday 24 June 2016 10:45 PM, Hari Bathini wrote:
On 06/24/2016 10:56 AM, Michael Ellerman wrote:
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote:
Currently, crashkernel parameter supports the below syntax to parse
size
based on memory range:
crashkernel
On 07/05/2016 10:48 AM, Michael Ellerman wrote:
On 06/24/2016 10:56 AM, Michael Ellerman wrote:
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote:
...
While the code is moved to kernel/params.c file, there is no change in logic
for crashkernel parameter parsing as the moved code
Hi Dave
Thanks for the review..
On Thursday 04 August 2016 02:56 PM, Dave Young wrote:
Hi Hari,
On 08/04/16 at 01:03am, Hari Bathini wrote:
crashkernel parameter supports different syntaxes to specify the amount
of memory to be reserved for kdump kernel. Below is one of the supported
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
...
/**
* fadump_calculate_reserve_size(): reserve variable boot area 5% of System
RAM
*
@@ -212,12 +262,17 @@ static inline unsigned long
fadump_calculate_reserv
On Friday 05 August 2016 12:23 AM, Hari Bathini wrote:
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
...
/**
* fadump_calculate_reserve_size(): reserve variable boot area 5%
of System RAM
*
@@ -212,12 +
On Monday 08 August 2016 02:26 PM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
On Friday 05 August 2016 12:23 AM, Hari Bathini wrote:
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
The code already knows how to reserve 5% based on th
region and appends these parameters to capture kernel early
in its boot process.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v1:
* Not changing dump format version to keep compatibility intact. Using
start and end markers instead, to check sanity of handove
Update documentation about introduction of handover area that includes
configuration details like extra parameters to append to capture
kernel.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Documentation/powerpc/firmware-assisted-dump.txt | 83 ++
Hi Mahesh,
On Tuesday 31 January 2017 01:05 AM, Mahesh Jagannath Salgaonkar wrote:
On 01/30/2017 10:14 PM, Hari Bathini wrote:
In case of fadump, capture (fadump) kernel boots like a normal kernel.
While this has its advantages, the capture kernel would initialize all
the components like
On Friday 20 January 2017 11:17 AM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
Get rid of multiple definitions of append_elf_note() & final_note()
functions. Reuse these functions compiled under CONFIG_CRASH_CORE
Also, define Elf_Word and use
On Tuesday 17 January 2017 10:36 PM, Hari Bathini wrote:
On Friday 06 January 2017 07:33 AM, Dave Young wrote:
On 01/05/17 at 11:01pm, Hari Bathini wrote:
Get rid of multiple definitions of append_elf_note() & final_note()
functions. Reuse these functions compiled under CONFIG_CRASH_
region and appends these parameters to capture kernel early
in its boot process.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/include/asm/fadump.h | 28
arch/powerpc/kernel/fadump.c | 125 -
arch/powerpc/
region and appends these parameters to capture kernel early
in its boot process.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/include/asm/fadump.h | 28
arch/powerpc/kernel/fadump.c | 125 -
arch/powerpc/
Update documentation about introduction of handover area that includes
configuration details like extra parameters to append to capture
kernel.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Documentation/powerpc/firmware-assisted-dump.txt | 83 ++
On Tuesday 24 January 2017 11:53 PM, Tony Luck wrote:
On Tue, Jan 24, 2017 at 10:11 AM, Hari Bathini
<hbath...@linux.vnet.ibm.com> wrote:
Hello IA64 folks,
Could you please review this patch..?
It looks OK in principal. My lab is in partial disarray at the
moment (just got bac
which doesn't take the holes, if any,
in the memory layout into account, use memblock_phys_mem_size() to
calculate the percentage of total available memory.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
This patch is based on top of the patchset to reuse-crashkernel-parameter
Hi Michael,
On Friday 17 February 2017 11:54 AM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadump.c
index de7d39a..d5107f4 100644
--- a/arch/powerpc/kernel/fadump.c
+++ b/arch/powerpc/
y size closer to 50% of the total available memory is specified.
As the kernel is not handling this currently, it may lead to undefined
behavior. Fix it by setting an upper limit for boot memory size to 25%
of the total available memory.
Signed-off-by: Hari Bathini <hbath...@linux.vne
On Friday 06 January 2017 07:33 AM, Dave Young wrote:
On 01/05/17 at 11:01pm, Hari Bathini wrote:
Get rid of multiple definitions of append_elf_note() & final_note()
functions. Reuse these functions compiled under CONFIG_CRASH_CORE
Also, define Elf_Word and use it instead of generic
Hi Michael/Aneesh,
Thanks for reviewing the patch..
On Friday 23 September 2016 04:40 PM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
diff --git a/arch/powerpc/include/asm/mmu.h b/arch/powerpc/include/asm/mmu.h
index e2fb408..558987c 100644
--- a/arch/p
On Friday 23 September 2016 10:14 AM, Aneesh Kumar K.V wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
Hi Aneesh,
On Thursday 22 September 2016 09:54 PM, Aneesh Kumar K.V wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
The kernel now supports both radix
introduces a new global variable, which holds the current MMU
mode the kernel is running in and can be accessed by tools early in thier
init process, helping tools to initialize accurately for each MMU mode.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/include/asm/boo
On Thursday 22 September 2016 09:32 PM, Hari Bathini wrote:
The kernel now supports both radix and hash MMU modes. Tools like crash
and makedumpfile need to know the current MMU mode the kernel is using,
to debug/analyze it. The current MMU mode depends on hardware support
and also whether
introduces a new global variable, which holds the current MMU
mode the kernel is running in and can be accessed by tools early in thier
init process, helping tools to initialize accurately for each MMU mode.
This patch also optimizes the radix_enabled() function call.
Signed-off-by: Hari Bathini
introduces a new global variable, which holds the current MMU
mode the kernel is running in and can be accessed by tools early in thier
init process, helping tools to initialize accurately for each MMU mode.
This patch also optimizes the radix_enabled() function call.
Signed-off-by: Hari Bathini
Hi Aneesh,
On Thursday 22 September 2016 09:54 PM, Aneesh Kumar K.V wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
The kernel now supports both radix and hash MMU modes. Tools like crash
and makedumpfile need to know the current MMU mode the kernel is using,
to debug/a
On Thursday 25 August 2016 12:31 PM, Dave Young wrote:
On 08/10/16 at 03:35pm, Hari Bathini wrote:
When fadump is enabled, by default 5% of system RAM is reserved for
fadump kernel. While that works for most cases, it is not good enough
for every case.
Currently, to override the default
As we are reusing crashkernel parameter instead of fadump_reserve_mem
parameter to specify the memory to reserve for fadump's crash kernel,
update the documentation accordingly.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Documentation/powerpc/firmware-assisted-dump.txt
,
allowing code reuse without dependency on CONFIG_KEXEC. While here,
removing the multiple definitions of append_elf_note() and final_note()
for one defined under CONFIG_CONFIG_CORE. There is no functional change
with this patch.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
for multiple syntaxes to specify memory.
Suggested-by: Dave Young <dyo...@redhat.com>
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/kernel/fadump.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/arch/po
of fadump_reserve_mem. This has the advantage of using
all the syntaxes crashkernel supports, for fadump as well. The third patch
updates fadump kernel documentation about use of crashkernel parameter.
---
Hari Bathini (3):
crash: move crashkernel parsing and vmcore related code under
CONFIG_CRASH_CORE
On Monday 14 November 2016 11:06 AM, Baoquan He wrote:
On 11/10/16 at 05:27pm, Hari Bathini wrote:
Traditionally, kdump is used to save vmcore in case of a crash. Some
architectures like powerpc can save vmcore using architecture specific
support instead of kexec/kdump mechanism
orts, for fadump as well. The last patch updates
fadump kernel documentation about use of crashkernel parameter.
Changes from v1:
* Moved arch specify code to seperate patches. Introduced one patch for IA64
arch
and another patch for powerpc in the process.
---
Hari Bathini (5):
crash:
ilar functions compiled under CONFIG_CRASH_CORE.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/powerpc/Kconfig | 10 ++
arch/powerpc/include/asm/fadump.h |2 ++
arch/powerpc/kernel/crash.c|2 --
arch/powerpc/kernel/fadump.c
As we are reusing crashkernel parameter instead of fadump_reserve_mem
parameter to specify the memory to reserve for fadump's crash kernel,
update the documentation accordingly.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Documentation/powerpc/firmware-assisted-dump.txt
,
allowing code reuse without dependency on CONFIG_KEXEC. There is no
functional change with this patch.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
arch/Kconfig |4
include/linux/crash_core.h | 71 +++
include/linux/kexec.h | 63 --
1 - 100 of 792 matches
Mail list logo
