available memory.
Signed-off-by: Hari Bathini
---
arch/powerpc/kernel/fadump.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadump.c
index 8ff0dd4..9c85c5a 100644
--- a/arch/powerpc/kernel/fadump.c
+++ b/ar
AM(), 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
---
This patch is based on top of the patchset to reuse-crashkernel-parameter-
for-fadump (http://patc
Hi Michael,
On Friday 17 February 2017 11:54 AM, Michael Ellerman wrote:
Hari Bathini 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/kernel/fadump.c
@@ -222,6 +222,18
memory 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
---
This patch is base
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
Update documentation about introduction of handover area that includes
configuration details like extra parameters to append to capture
kernel.
Signed-off-by: Hari Bathini
---
Documentation/powerpc/firmware-assisted-dump.txt | 83 ++
1 file changed, 53 insertions(+), 30
region and appends these parameters to capture kernel early
in its boot process.
Signed-off-by: Hari Bathini
---
Changes from v1:
* Not changing dump format version to keep compatibility intact. Using
start and end markers instead, to check sanity of handover area.
* Checking for memory overlap
region and appends these parameters to capture kernel early
in its boot process.
Signed-off-by: Hari Bathini
---
arch/powerpc/include/asm/fadump.h | 28
arch/powerpc/kernel/fadump.c | 125 -
arch/powerpc/kernel/prom.c| 19 ++
3
Update documentation about introduction of handover area that includes
configuration details like extra parameters to append to capture
kernel.
Signed-off-by: Hari Bathini
---
Documentation/powerpc/firmware-assisted-dump.txt | 83 ++
1 file changed, 53 insertions(+), 30
region and appends these parameters to capture kernel early
in its boot process.
Signed-off-by: Hari Bathini
---
arch/powerpc/include/asm/fadump.h | 28
arch/powerpc/kernel/fadump.c | 125 -
arch/powerpc/kernel/prom.c| 19 ++
3
On Tuesday 24 January 2017 11:53 PM, Tony Luck wrote:
On Tue, Jan 24, 2017 at 10:11 AM, Hari Bathini
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 back from a sabbatical) so I can't
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_
On Friday 20 January 2017 11:17 AM, Michael Ellerman wrote:
Hari Bathini 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 it instead of generic u32 or the more
spec
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 u3
Hi Dave,
On Thursday 05 January 2017 11:47 AM, Dave Young wrote:
Hi, Hari
On 01/02/17 at 07:43pm, 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
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
---
Documentation/powerpc/firmware-assisted-dump.txt | 23 ++--
nd support
for multiple syntaxes to specify memory.
Suggested-by: Dave Young
Signed-off-by: Hari Bathini
---
arch/powerpc/kernel/fadump.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadu
ilar functions compiled under CONFIG_CRASH_CORE.
Signed-off-by: Hari Bathini
---
arch/powerpc/Kconfig | 10 ++
arch/powerpc/include/asm/fadump.h |2 ++
arch/powerpc/kernel/crash.c|2 --
arch/powerpc/kernel/fadump.c |
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 u32 or the more
specific Elf64_Word.
Signed-off-by: Hari Bathini
---
Changes from v3:
* Dropped hard-c
,
allowing code reuse without dependency on CONFIG_KEXEC. There is no
functional change with this patch.
Signed-off-by: Hari Bathini
---
Changes from v3:
* Renamed log_buf_kexec_setup()to log_buf_vmcoreinfo_setup() instead of
log_buf_crash_setup().
Changes from v2:
* Used CONFIG_CRASH_CORE
orts, for fadump as well. The last patch updates
fadump kernel documentation about use of crashkernel parameter.
---
Hari Bathini (5):
crash: move crashkernel parsing and vmcore related code under
CONFIG_CRASH_CORE
ia64: reuse append_elf_note() and final_note() functions
pow
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
---
Documentation/powerpc/firmware-assisted-dump.txt | 23 ++--
nd support
for multiple syntaxes to specify memory.
Suggested-by: Dave Young
Signed-off-by: Hari Bathini
---
arch/powerpc/kernel/fadump.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadu
ilar functions compiled under CONFIG_CRASH_CORE.
Signed-off-by: Hari Bathini
---
arch/powerpc/Kconfig | 10 ++
arch/powerpc/include/asm/fadump.h |2 ++
arch/powerpc/kernel/crash.c|2 --
arch/powerpc/kernel/fadump.c |
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 u32 or the more
specific Elf64_Word.
Signed-off-by: Hari Bathini
---
Changes from v2:
* Added a defini
,
allowing code reuse without dependency on CONFIG_KEXEC. There is no
functional change with this patch.
Signed-off-by: Hari Bathini
---
Changes from v2:
* Used CONFIG_CRASH_CORE instead of CONFIG_KEXEC_CORE at
appropriate places in printk and ksysfs.
arch/Kconfig |4
orts, for fadump as well. The last patch updates
fadump kernel documentation about use of crashkernel parameter.
---
Hari Bathini (5):
crash: move crashkernel parsing and vmcore related code under
CONFIG_CRASH_CORE
ia64: reuse append_elf_note() and final_note() functions
pow
On Saturday 03 December 2016 12:52 AM, Eric W. Biederman wrote:
Hari Bathini writes:
Hi Dave,
Thanks for the review.
On Thursday 01 December 2016 10:26 AM, Dave Young wrote:
Hi Hari
Personally I like V1 more, but split the patch 2 is easier for ia64
people to reivew. I did basic x86
Hi Dave,
Thanks for the review.
On Thursday 01 December 2016 10:26 AM, Dave Young wrote:
Hi Hari
Personally I like V1 more, but split the patch 2 is easier for ia64
people to reivew. I did basic x86 testing, it runs ok.
On 11/25/16 at 05:24pm, Hari Bathini wrote:
Get rid of multiple
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
---
Documentation/powerpc/firmware-assisted-dump.txt | 23 ++--
nd support
for multiple syntaxes to specify memory.
Suggested-by: Dave Young
Signed-off-by: Hari Bathini
---
arch/powerpc/kernel/fadump.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadu
ilar functions compiled under CONFIG_CRASH_CORE.
Signed-off-by: Hari Bathini
---
arch/powerpc/Kconfig | 10 ++
arch/powerpc/include/asm/fadump.h |2 ++
arch/powerpc/kernel/crash.c|2 --
arch/powerpc/kernel/fadump.c |
Get rid of multiple definitions of append_elf_note() & final_note()
functions. Reuse these functions compiled under CONFIG_CRASH_CORE.
Signed-off-by: Hari Bathini
---
arch/ia64/kernel/crash.c | 22 --
include/linux/crash_core.h |4
kernel/crash_co
,
allowing code reuse without dependency on CONFIG_KEXEC. There is no
functional change with this patch.
Signed-off-by: Hari Bathini
---
arch/Kconfig |4
include/linux/crash_core.h | 71 +++
include/linux/kexec.h | 63 --
kernel/Makefile|1
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:
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. Such
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
---
Documentation/powerpc/firmware-assisted-dump.txt | 23 ++--
nd support
for multiple syntaxes to specify memory.
Suggested-by: Dave Young
Signed-off-by: Hari Bathini
---
arch/powerpc/kernel/fadump.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadump.c
ind
,
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
---
arch/Kconfig
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
Hi Michael/Aneesh,
Thanks for reviewing the patch..
On Friday 23 September 2016 04:40 PM, Michael Ellerman wrote:
Hari Bathini writes:
diff --git a/arch/powerpc/include/asm/mmu.h b/arch/powerpc/include/asm/mmu.h
index e2fb408..558987c 100644
--- a/arch/powerpc/include/asm/mmu.h
+++ b/arch
On Friday 23 September 2016 10:14 AM, Aneesh Kumar K.V wrote:
Hari Bathini writes:
Hi Aneesh,
On Thursday 22 September 2016 09:54 PM, Aneesh Kumar K.V wrote:
Hari Bathini writes:
The kernel now supports both radix and hash MMU modes. Tools like crash
and makedumpfile need to know the
Hi Aneesh,
On Thursday 22 September 2016 09:54 PM, Aneesh Kumar K.V wrote:
Hari Bathini 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/analyze it. The current MMU mode depends
patch 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 Ba
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
patch 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 Ba
patch 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
---
arch/powerpc/include/asm/book3s/64/mmu.h |5 +
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
s.
Signed-off-by: Hari Bathini
Reviewed-by: Mahesh J Salgaonkar
---
Changes from v2:
1. Updated changelog
arch/powerpc/kernel/fadump.c | 63 --
1 file changed, 54 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powe
se in parsing the crashkernel
parameter.
Signed-off-by: Hari Bathini
---
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 |
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
On Monday 08 August 2016 02:26 PM, Michael Ellerman wrote:
Hari Bathini 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 the size of the
machine's
memory, as lo
On Friday 05 August 2016 12:23 AM, Hari Bathini wrote:
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
Hari Bathini writes:
...
/**
* fadump_calculate_reserve_size(): reserve variable boot area 5%
of System RAM
*
@@ -212,12 +262,17 @@ static inline unsigned long
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 writes:
...
/**
* fadump_calculate_reserve_size(): reserve variable boot area 5% of System
RAM
*
@@ -212,12 +262,17 @@ static inline unsigned long
fadump_calculate_reserve_size(void)
{
unsigned long
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini
Reviewed-by: Mahesh J Salgaonkar
---
arch/powerpc/kernel/fadump.c | 64 --
1 file changed, 55 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc
se in parsing the crashkernel
parameter.
Signed-off-by: Hari Bathini
---
Changes from v1:
1. Updated changelog
include/linux/kernel.h |5 +++
kernel/kexec_core.c| 63 +++-
kernel/params.c| 96
3 files ch
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
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 is
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
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini
Reviewed-by: Mahesh J Salgaonkar
---
Changes in v2:
1. Changed subject from "[PATCH v2 2/2] powerpc/fadump: add support to parse
size based on memory range".
2. Rebased to latest upstream.
arch/powerpc/kerne
.
Cc: Eric Biederman
Cc: Vivek Goyal
Cc: Rusty Russell
Cc: ke...@lists.infradead.org
Signed-off-by: Hari Bathini
---
changes in v2:
1. Rebased to latest upstream.
2. Marked few more people on cc.
include/linux/kernel.h |5 +++
kernel/kexec_core.c| 63
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
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini
---
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 (see patch
1/2)
arch/powerpc/kerne
.
Signed-off-by: Hari Bathini
---
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/params.c| 96
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
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 '
y: Mahesh Salgaonkar
Signed-off-by: Hari Bathini
---
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/arch/powerpc/kernel/fadump.c
+++ b/arch/pow
using the same commandline parameter for different system
memory sizes.
Signed-off-by: Hari Bathini
---
arch/powerpc/kernel/fadump.c | 127 +++---
1 file changed, 118 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel
-off-by: Hari Bathini
---
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..2c3cb32 100644
--- a/arch/powerpc/include
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
fault/production kernel and kdump kernel.
Signed-off-by: Hari Bathini
Signed-off-by: Mahesh Salgaonkar
---
Michael, I did test this patchset in different scenarios. But if you feel
the change is too radical, we could go with version2. But I thought this was
worth a shot.
changes from v3:
1. No ch
x27;vmlinux' failed
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 b
good 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
---
arch/powerpc/kernel/exceptions-64s.S | 13 +
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 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 by
fault/production kernel and kdump kernel.
Signed-off-by: Hari Bathini
Signed-off-by: Mahesh Salgaonkar
---
changes from v2:
2. Move the OOL handlers before __end_interrupts marker instead of moving the
__end_interrupts marker
3. Leave __end_handlers marker as is.
arch/powerpc/kernel/exceptions-
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 neede
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
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
ested 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
Signed-off-by: Mahesh Salgaonkar
---
changes from v1:
1. Changed the subject from "copy interrupts till __end_handlers marker
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
0 as executable, 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
On 11/05/2015 07:02 AM, David Gibson wrote:
On Wed, 4 Nov 2015 14:54:51 +0100
Laurent Vivier 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 kernel, this is not done in
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 t
This
patch removes the error message in case "pstore.backend != nvram".
Signed-off-by: Hari Bathini
---
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 1e7
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
This patch series is reviewed by Kees
While we are here, let us make timestamp related code
y2038-safe.
Suggested-by: Arnd Bergmann
Signed-off-by: Hari Bathini
---
arch/powerpc/include/asm/rtas.h|3 ++-
arch/powerpc/kernel/nvram_64.c |6 +++---
arch/powerpc/platforms/pseries/nvram.c | 10 +-
3
ces, where 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
---
arch/powerpc/kernel/nvram_64.c | 25 +++-
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
---
fs/pstore/inode.c |3 +++
include/linux/pstore.h |1 +
2 files changed
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
---
arch/powerpc/include/asm/nvram.h
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 gen
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
ces, where 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
Cc: Anton Vorontsov
Cc: Colin Cross
Cc: Kees Cook
Cc: Tony Luck
---
arch
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
Cc: Anton Vorontsov
Cc: Colin Cross
Cc: Kees Cook
Cc: Tony Luck
---
fs/pstore/inode.c
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
---
arch/powerpc/include/asm/nvram.h
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 Bathin
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/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
701 - 800 of 819 matches
Mail list logo
