From: Mahesh Salgaonkar
This patch introduces an sysfs interface '/sys/kernel/fadump_release_mem' to
invalidate the last fadump registration, invalidate '/proc/vmcore', release
the reserved memory for general use and re-register for future kernel dump.
Once the dump is copied to the disk, the use
From: Mahesh Salgaonkar
Remove the phyp assisted dump implementation which is not is use.
Signed-off-by: Mahesh Salgaonkar
---
Documentation/powerpc/phyp-assisted-dump.txt | 127 --
arch/powerpc/Kconfig | 10 -
arch/powerpc/include/asm/phyp_dump.h | 47
From: Mahesh Salgaonkar
If dump is active during system reboot, shutdown or halt then invalidate
the fadump registration as it does not get invalidated automatically.
Signed-off-by: Mahesh Salgaonkar
---
arch/powerpc/kernel/setup-common.c |8
1 files changed, 8 insertions(+), 0 de
From: Mahesh Salgaonkar
When registered for firmware assisted dump on powerpc, firmware preserves
the registers for the active CPUs during a system crash. This patch reads
the cpu register data stored in Firmware-assisted dump format (except for
crashing cpu) and converts it into elf notes and up
From: Mahesh Salgaonkar
With the firmware-assisted dump support we don't require a reboot when we
are in second kernel after crash. The second kernel after crash is a normal
kernel boot and has knowledge about entire system RAM with the page tables
initialized for entire system RAM. Hence once th
From: Mahesh Salgaonkar
Introduce a PT_NOTE program header that points to physical address of
vmcoreinfo_note buffer declared in kernel/kexec.c. The vmcoreinfo
note buffer is populated during crash_fadump() at the time of system
crash.
Signed-off-by: Mahesh Salgaonkar
---
arch/powerpc/kernel/f
From: Mahesh Salgaonkar
Reserve the memory during early boot to preserve CPU state data, HPTE region
and RMA (real mode area) region data in case of kernel crash. At the time of
crash, powerpc firmware will store CPU state data, HPTE region data and move
RMA region data to the reserved memory are
From: Mahesh Salgaonkar
Build the crash memory range list by traversing through system memory during
the first kernel before we register for firmware-assisted dump. After the
successful dump registration, initialize the elfcore header and populate
PT_LOAD program headers with crash memory ranges.
From: Mahesh Salgaonkar
This patch registers for firmware-assisted dump using rtas token
ibm,configure-kernel-dump. During registration firmware is informed about
the reserved area where it saves the CPU state data, HPTE table and contents
of RMR region at the time of kernel crash. Apart from thi
From: Mahesh Salgaonkar
Documentation for firmware-assisted dump. This document is based on the
original documentation written for phyp assisted dump by Linas Vepstas
and Manish Ahuja, with few changes to reflect the current implementation.
Signed-off-by: Mahesh Salgaonkar
---
Documentation/po
Hi All,
Please find the version 6 of the patchset that implements firmware-assisted
dump mechanism to capture kernel crash dump for Powerpc architecture. The
firmware-assisted dump is a robust mechanism to get reliable kernel crash
dump with assistance from firmware. This approach does not use kex
On 11/25/2011 04:04 AM, Paul Mackerras wrote:
>> + /sys/kernel/debug/powerpc/fadump_region
>> +
>> +This file shows the reserved memory regions if fadump is
>> +enabled otherwise this file is empty. The output format
>> +is:
>> +: [-] bytes, Dumped:
>> +
>> +e.g.
>> +Conte
On 12/09/11 17:13, Suzuki K. Poulose wrote:
The following series implements:
* Generic framework for relocatable kernel on PPC32, based on processing
the dynamic relocation entries.
* Relocatable kernel support for 44x
* Kdump support for 44x. Doesn't support 47x yet, as the kexec
On Tue, Dec 06, 2011 at 10:39:57PM -0500, Paul Gortmaker wrote:
> Hi Greg,
>
> This is the Freescale hardware bug fix which turned into a
> six-pack of 8250 updates. This is exactly what was posted
> in the v2 review, with just Alan's ack added[1]. Since nobody
> else has had any follow-on comme
The following patch implements the dynamic relocation processing for
PPC32 kernel. relocate() accepts the target virtual address and relocates
the kernel image to the same.
Currently the following relocation types are handled :
R_PPC_RELATIVE
R_PPC_ADDR16_LO
R_PPC_ADDR16_
On 12/09/11 19:10, Josh Boyer wrote:
On Fri, Dec 9, 2011 at 6:47 AM, Suzuki K. Poulose wrote:
Signed-off-by: Suzuki K. Poulose
Signed-off-by: Josh Poimboeuf
Cc: Paul Mackerras
Cc: Benjamin Herrenschmidt
Cc: Alan Modra
Cc: Kumar Gala
Cc: linuxppc-dev
---
arch/powerpc/Kconfig |
Hi Andreas,
> There is no user of usecs_to_cputime before 3.2-rc1, so it wouldn't
> have any effect for older versions.
Great, that explains why I only noticed it last week :)
Anton
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://l
Anton Blanchard writes:
> Hi Andreas,
>
>> Commit d57af9b (taskstats: use real microsecond granularity for CPU
>> times) renamed msecs_to_cputime to usecs_to_cputime, but failed to
>> update all numbers on the way. This causes nonsensical cpu
>> idle/iowait values to be displayed in /proc/stat (
Hi Andreas,
> Commit d57af9b (taskstats: use real microsecond granularity for CPU
> times) renamed msecs_to_cputime to usecs_to_cputime, but failed to
> update all numbers on the way. This causes nonsensical cpu
> idle/iowait values to be displayed in /proc/stat (the only user of
> usecs_to_cputi
On Friday 09 December 2011 13:48:52 Andrew Morton wrote:
> What would we need to do to get all architectures using the new
> interfaces, and remove __ARCH_WANT_OLD_COMPAT_IPC?
We would change the various compat_sys_ipc functions (mips, powerpc,
s390, sparc, x86) to call the new functions instead o
On Mon, Oct 10, 2011 at 3:50 PM, Becky Bruce wrote:
> From: Becky Bruce
>
> Results from updates via make savedefconfig.
>
> Signed-off-by: Becky Bruce
> ---
...
> -CONFIG_PPC_EPAPR_HV_BYTECHAN=y
I guess no one noticed that this patch removes byte channel support,
thereby preventing this kern
On Fri, 9 Dec 2011 10:29:07 -0500
Chris Metcalf wrote:
> When using the "compat" APIs, architectures will generally want to
> be able to make direct syscalls to msgsnd(), shmctl(), etc., and
> in the kernel we would want them to be handled directly by
> compat_sys_xxx() functions, as is true for
Commit d57af9b (taskstats: use real microsecond granularity for CPU times)
renamed msecs_to_cputime to usecs_to_cputime, but failed to update all
numbers on the way. This causes nonsensical cpu idle/iowait values to be
displayed in /proc/stat (the only user of usecs_to_cputime so far).
This also
On Thu, Nov 24, 2011 at 1:40 PM, Kumar Gala wrote:
> arch/powerpc/mm/hugetlbpage.c: In function 'reserve_hugetlb_gpages':
> arch/powerpc/mm/hugetlbpage.c:312:2: error: implicit declaration of function
> 'parse_args'
>
> Signed-off-by: Kumar Gala
Acked-by: Timur Tabi
Would you please apply thi
On 12/09/2011 03:42 AM, shuo@freescale.com wrote:
> From: Liu Shuo
>
> Freescale FCM controller has a 2K size limitation of buffer RAM. In order
> to support the Nand flash chip whose page size is larger than 2K bytes,
> we read/write 2k data repeatedly by issuing FIR_OP_RB/FIR_OP_WB and save
On 12/09/2011 03:42 AM, shuo@freescale.com wrote:
> From: Liu Shuo
>
> If we use the Nand flash chip whose number of pages in a block is greater
> than 64(for large page), we must treat the low bit of FBAR as being the
> high bit of the page address due to the limitation of FCM, it simply use
When using the "compat" APIs, architectures will generally want to
be able to make direct syscalls to msgsnd(), shmctl(), etc., and
in the kernel we would want them to be handled directly by
compat_sys_xxx() functions, as is true for other compat syscalls.
However, for historical reasons, several
On Thu, December 8, 2011 9:33 pm, Jeremy Fitzhardinge wrote:
> On 12/08/2011 05:27 PM, Tony Breeds wrote:
>> Commit 4f5ca836bef3 (HID: hid-input: add support for HID devices
>> reporting Battery Strength) went into linux-next on Dec 1st since then a
>> ppc6xx_defconfig has been failing with:
>>
>>
On 12/09/2011 03:27 AM, Liu Shengzhou-B36685 wrote:
> Before calling nand_scan_ident(), we can still use 2k FCM RAM, not need a
> buffer greater than 2k，
> After nand_scan_ident(), if writesize > 2048, then allocate a large buffer.
> We can do it in fsl_elbc_chip_init_tail()
> if (mtd->writesiz
On Sun, Nov 27, 2011 at 01:27:41PM +0800, Cong Wang wrote:
Acked-by: Ralf Baechle
Ralf
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Signed-off-by: Timur Tabi
---
arch/powerpc/boot/dts/p1022ds.dts | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/powerpc/boot/dts/p1022ds.dts
b/arch/powerpc/boot/dts/p1022ds.dts
index e627f70..d4c1439 100644
--- a/arch/powerpc/boot/dts/p1022ds.dts
+++ b/arch
Create a 32-bit address space version of p1022ds.dts. To avoid confusion,
p1022ds.dts is renamed to p1022ds_36b.dts. We also create p1022ds.dtsi
to store some common nodes.
Signed-off-by: Timur Tabi
---
arch/powerpc/boot/dts/p1022ds.dts | 270 -
arch/powerp
The Freescale P1022 has a unique pin muxing "feature" where the DIU video
controller's video signals are muxed with 24 of the local bus address signals.
When the DIU is enabled, the bulk of the local bus is disabled, preventing
access to memory-mapped devices like NOR flash and the pixis FPGA.
The
On Wed, Nov 30, 2011 at 10:14 AM, Josh Boyer wrote:
> Hi Ben,
>
> I have a new 4xx tree setup now. Two small commits for the next
> branch are queued up. I'd like to get the patch series from Suzie and
> Tony included soon as well, but thought I'd start with these to get
> things rolling.
I've
On Fri, Dec 9, 2011 at 6:47 AM, Suzuki K. Poulose wrote:
>
> Signed-off-by: Suzuki K. Poulose
> Signed-off-by: Josh Poimboeuf
> Cc: Paul Mackerras
> Cc: Benjamin Herrenschmidt
> Cc: Alan Modra
> Cc: Kumar Gala
> Cc: linuxppc-dev
> ---
>
> arch/powerpc/Kconfig | 42
> +++
Greetings All,
I am doing a dual boot on P1022RDK with following configuration
Core 0: Linux RT: Running fine, ethernet@B is working fine.
Core 1: Linux: Crashing at following, ethernet@B1000 is not creating a link
I have allocated ethernet1 to core 1 in its DTS file but when I boot my kerne
The wrapper code which uncompresses the kernel in case of a 'ppc' boot
is by default loaded at 0x0040 and the kernel will be uncompressed
to fit the location 0-0x0040. But with dynamic relocations, the size
of the kernel may exceed 0x0040(4M). This would cause an overlap
of the uncompre
Now that we have relocatable kernel, supporting CRASH_DUMP only requires
turning the switches on for UP machines.
We don't have kexec support on 47x yet. Enabling SMP support would be done
as part of enabling the PPC_47x support.
Signed-off-by: Suzuki K. Poulose
Cc: Josh Boyer
Cc: Benjamin Her
The following patch adds relocatable kernel support - based on processing
of dynamic relocations - for PPC44x kernel.
We find the runtime address of _stext and relocate ourselves based
on the following calculation.
virtual_base = ALIGN(KERNELBASE,256M) +
MODULO(_st
We find the runtime address of _stext and relocate ourselves based
on the following calculation.
virtual_base = ALIGN(KERNELBASE,KERNEL_TLB_PIN_SIZE) +
MODULO(_stext.run,KERNEL_TLB_PIN_SIZE)
relocate() is called with the Effective Virtual Base Address (as
shown bel
The following patch implements the dynamic relocation processing for
PPC32 kernel. relocate() accepts the target virtual address and relocates
the kernel image to the same.
Currently the following relocation types are handled :
R_PPC_RELATIVE
R_PPC_ADDR16_LO
R_PPC_ADDR16_
DYNAMIC_MEMSTART(old RELOCATABLE) was restricted only to PPC_47x variants
of 44x. This patch enables DYNAMIC_MEMSTART for 440x based chipsets.
Signed-off-by: Suzuki K. Poulose
Cc: Josh Boyer
Cc: Kumar Gala
Cc: Benjamin Herrenschmidt
Cc: linux ppc dev
---
arch/powerpc/Kconfig |
The current implementation of CONFIG_RELOCATABLE in BookE is based
on mapping the page aligned kernel load address to KERNELBASE. This
approach however is not enough for platforms, where the TLB page size
is large (e.g, 256M on 44x). So we are renaming the RELOCATABLE used
currently in BookE to DYN
The following series implements:
* Generic framework for relocatable kernel on PPC32, based on processing
the dynamic relocation entries.
* Relocatable kernel support for 44x
* Kdump support for 44x. Doesn't support 47x yet, as the kexec
support is missing.
Changes from V3:
* Added a
From: Liu Shuo
Freescale FCM controller has a 2K size limitation of buffer RAM. In order
to support the Nand flash chip whose page size is larger than 2K bytes,
we read/write 2k data repeatedly by issuing FIR_OP_RB/FIR_OP_WB and save
them to a large buffer.
Signed-off-by: Liu Shuo
Signed-off-by
From: Liu Shuo
If we use the Nand flash chip whose number of pages in a block is greater
than 64(for large page), we must treat the low bit of FBAR as being the
high bit of the page address due to the limitation of FCM, it simply uses
the low 6-bits (for large page) of the combined block/page add
kevin diggs writes:
> On 12/8/11, Andreas Schwab wrote:
>> There seems to be something wrong with cpu idle time accounting at least
>> on G5. The value as reported in the cpu lines in /proc/stat seems to be
>> stuck in the interval [10,21] for each cpu, jumping back at
>> random points.
> -Original Message-
>
> Message: 4
> Date: Sun, 4 Dec 2011 12:31:38 +0800
> From:
> To: , ,
>
> Cc: linux-ker...@vger.kernel.org, shuo@freescale.com,
> linux-...@lists.infradead.org, a...@linux-foundation.org,
> linuxppc-dev@lists.ozlabs.org
> Subject: [PATCH 3/3
48 matches
Mail list logo
