remove cast for kmalloc/kzalloc return value.
Signed-off-by: Zhang Yanfei
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Andrew Morton
Cc: linuxppc-dev@lists.ozlabs.org
---
arch/powerpc/kernel/nvram_64.c |3 +--
arch/powerpc/kvm/book3s_pr.c |2 +-
2 files changed, 2 insertions(+)
On Fri, Feb 15, 2013 at 09:09:38PM +0530, Aneesh Kumar K.V wrote:
> From: "Aneesh Kumar K.V"
>
> This patch change the kernel VSID range so that we limit VSID_BITS to 37.
> This enables us to support 64TB with 65 bit VA (37+28). Without this patch
> we have boot hangs on platforms that only suppo
On Tue, 2013-03-12 at 08:28 +0530, Aneesh Kumar K.V wrote:
> Ben, Paul,
>
> Any update on this ?
Paul and David are reviewing it and I was trying to test on POWER3 (STAB
vs. SLB) but ended up bisecting instead why POWER3 stopped working in
3.4 ... :-)
Cheers,
Ben.
Ben, Paul,
Any update on this ?
-aneesh
"Aneesh Kumar K.V" writes:
> From: "Aneesh Kumar K.V"
>
> This patch change the kernel VSID range so that we limit VSID_BITS to 37.
> This enables us to support 64TB with 65 bit VA (37+28). Without this patch
> we have boot hangs on platforms that on
With some CONFIGS it's possible that in ppc_set_hwdebug, brk.len is
uninitialised before being used. It has been reported that GCC 4.2 will
produce the following error in this case:
arch/powerpc/kernel/ptrace.c:1479: warning: 'brk.len' is used uninitialized
in this function
arch/powerpc/kern
On 03/09/2013 03:22 AM, Gala Kumar-B11780 wrote:
On Mar 8, 2013, at 2:32 AM, Chunhe Lan wrote:
Adding pcie error interrupt edac support for mpc85xx, p3041, p4080,
and p5020. The mpc85xx uses the legacy interrupt report mechanism -
the error interrupts are reported directly to mpic. While, the p
On Mon, 2013-03-11 at 17:41 -0700, Geoff Levand wrote:
> I didn't seen this fix go in for 3.8. Did I miss it, or is there some
> reason we don't want it?
>
> I need this to boot PS3.
Working on it. There's a couple of issues, among others testing on STAB
and a couple of comments from David, I'm
Hi,
On Fri, 2013-02-15 at 21:09 +0530, Aneesh Kumar K.V wrote:
> From: "Aneesh Kumar K.V"
>
> This patch change the kernel VSID range so that we limit VSID_BITS to 37.
> This enables us to support 64TB with 65 bit VA (37+28). Without this patch
> we have boot hangs on platforms that only support
Hello Benjamin Herrenschmidt:
how about this patch ? is it correct ?
thanks.
:-)
gchen.
于 2013年01月24日 12:14, Chen Gang 写道:
>
> for tmp_part->header.name:
> it is "Terminating null required only for names < 12 chars".
> so need to limit the %.12s for it in printk
>
> addit
The Kconfig symbol PCI_PERMEDIA got removed in v2.6.24, through commit
e6b6e3ffb9ee8926f9f2f7dc9147df73e27d5828 ("[POWERPC] Remove APUS support
from arch/ppc"). Remove its last occurrence.
Signed-off-by: Paul Bolle
---
Tested with "make ARCH=powerpc menuconfig" using ps3_defconfig, both
before an
The Kconfig symbol POWER4_ONLY got removed in commit
694caf0255dcab506d1e174c96a65ab65d96e108 ("powerpc: Remove
CONFIG_POWER4_ONLY"). Remove its last traces.
Signed-off-by: Paul Bolle
---
Untested.
arch/powerpc/platforms/Kconfig.cputype | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-
On Sun, 2013-03-10 at 15:07 +0200, Adrian-Leonard Radu wrote:
> Signed-off-by: Adrian-Leonard Radu
> ---
> arch/powerpc/kernel/iommu.c |2 +-
> arch/powerpc/kernel/time.c |4 +---
> arch/powerpc/platforms/ps3/time.c|4 +---
> arch/powerpc/sysdev/rtc_cmos_setup.c
On 03/10/2013 01:52 PM, Benjamin Herrenschmidt wrote:
On Sun, 2013-03-10 at 11:53 +0100, Phileas Fogg wrote:
Good news :) I found the bug.
MMU features were not set properly for PPC970MP DD1.0 which,
unfortunately, my machine has.
Damn, one line fix but one week searching.
Linux 3.8.2 boots with
On Mar 11, 2013, at 9:47 AM, Rojhalat Ibrahim wrote:
> Hi,
>
> this issue was brought up before.
> See this thread:
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2012-July/099529.html
>
> The following patch works for me.
> Hot-added devices appear after "echo 1 > /sys/bus/pci/rescan".
>
On Mon, 2013-03-11 at 09:20 -0700, Olof Johansson wrote:
> On Mon, Mar 11, 2013 at 8:34 AM, Artem Bityutskiy wrote:
> > Hi MTD folks,
> >
> > we have huge amount of drivers, espacially mapping drives in
> > 'drivers/mtd', and for sure may of them are for ancient devices which
> > are long dead and
On Mon, Mar 11, 2013 at 8:34 AM, Artem Bityutskiy wrote:
> Hi MTD folks,
>
> we have huge amount of drivers, espacially mapping drives in
> 'drivers/mtd', and for sure may of them are for ancient devices which
> are long dead and not supported by modern kernels anyway. I would like
> to do a small
Rojhalat Ibrahim wrote on 2013/03/11 15:47:30:
>
> Hi,
>
> this issue was brought up before.
> See this thread:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2012-July/099529.html
>
> The following patch works for me.
> Hot-added devices appear after "echo 1 > /sys/bus/pci/rescan".
> I test
Hi,
this issue was brought up before.
See this thread:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2012-July/099529.html
The following patch works for me.
Hot-added devices appear after "echo 1 > /sys/bus/pci/rescan".
I tested it with a P5020DS development system.
Signed-off-by: Rojhalat I
From: Wei Yongjun
Use for_each_compatible_node() macro instead of open coding it.
Signed-off-by: Wei Yongjun
---
arch/powerpc/include/asm/parport.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/powerpc/include/asm/parport.h
b/arch/powerpc/include/asm/parport.h
in
When we're in kgdb_singlestep(), we have to work around to get
thread_info by copying from the kernel stack before calling
kgdb_handle_exception(), then copying it back afterwards.
But for PPC64, we have a lazy interrupt implementation. So after
copying thread info frome kernle stack, if we need t
Use DEFINE_PER_CPU to allocate thread_info statically instead of kmalloc().
This can avoid introducing more memory check codes.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/kgdb.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/kgdb.c b/arch/
We can't look up the address of the entry point of the function simply
via that function symbol for all architectures.
For PPC64 ABI, actually there is a function descriptors structure.
A function descriptor is a three doubleword data structure that contains
the following values:
* The fi
Currently we need to skip this for supporting KGDB.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/exceptions-64e.S |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/exceptions-64e.S
b/arch/powerpc/kernel/exceptions-64e.S
index 7df9a1f..fd5d61b 10
gdb always need to generate a single step properly to invoke
a kgdb state. But with lazy interrupt, book3e can't always
trigger a debug exception with a single step since the current
is blocked for handling those pending exception, then we miss
that expected dbcr configuration at last to generate a
We need to store thread info to these exception thread info like something
we already did for PPC32.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/exceptions-64e.S | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/powerpc/kernel/exceptions-64e.S
b/arch/powerpc/ker
We always alloc critical/machine/debug check exceptions. This is
different from the normal exception. So we should load these exception
stack properly like we did for booke.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/exceptions-64e.S | 49 +++---
1 file chan
This patchset is used to support kgdb/gdb on book3e.
Validated on p4080ds and p5040ds with test single step and breakpoint
v4:
* use DEFINE_PER_CPU to allocate kgdb's thread_info
* add patch 7 to make usre copy thread_info only !__check_irq_replay
* leave "andi. r14,r11,MSR_PR" out of "#ifndef
On 03/11/2013 09:33 AM, tiejun.chen wrote:
On 03/11/2013 06:39 AM, Alex Grad wrote:
While at it, check kmalloc return value.
Signed-off-by: Alex Grad
---
arch/powerpc/kernel/kgdb.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/kgdb.c b/arch/p
Use DEFINE_PER_CPU to allocate thread_info statically instead of kmalloc().
This can avoid introducing more memory check codes.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/kgdb.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/kgdb.c b/arch/
> -Original Message-
> From: Timur Tabi [mailto:ti...@tabi.org]
> Sent: Friday, March 08, 2013 10:17 PM
> To: Singh Sandeep-B37400
> Cc: linuxppc-dev@lists.ozlabs.org; Aggrwal Poonam-B10812
> Subject: Re: [PATCH 3/4] TDM Device Tree entries for various Freescale
> Platforms
>
> On Thu, Ma
30 matches
Mail list logo
