Changes from V1: Uses a tmp mapping in the other address space to setup
the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
Note: Should we do the same for kernel entry code for PPC44x ?
This patch adds kexec support for PPC440 based chipsets.This work is based
on the KEXEC
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 divide a page into multi-2K pages for MTD layer driver. In that case,
we force to set the page size to 2K bytes. We convert the page
PPC32 ELF ABI expects r2 to be loaded with Thread Pointer, which is 0x7000
bytes past the end of TCB. Though the purgatory is single threaded, it uses
TCB scratch space in vsnprintf(). This patch allocates a 1024byte TCB
and populates the TP with the address accordingly.
Changes from V1: Fixed the
Hi Kumar,
On Mon, Jun 20, 2011 at 07:56:10AM +0300, Baruch Siach wrote:
> CONFIG_E500MC breaks e500/e500v2 systems. It defines L1_CACHE_SHIFT to 6, thus
> breaking clear_pages(), probably others too.
Ping?
Ack/Nack?
baruch
> Cc: Kumar Gala
> Signed-off-by: Baruch Siach
> ---
> Is this the rig
On Mon, 2011-07-11 at 22:51 -0500, Kumar Gala wrote:
> On Jul 11, 2011, at 12:52 AM, Michael Neuling wrote:
>
> > On POWER6 and POWER7 if the input operand to an instruction is a
> > denormalised single precision binary floating we can take a
> > denormalisation exception where it's expected that
On Jul 11, 2011, at 12:52 AM, Michael Neuling wrote:
> On POWER6 and POWER7 if the input operand to an instruction is a
> denormalised single precision binary floating we can take a
> denormalisation exception where it's expected that the hypervisor (HV=1)
> will fix up the inputs before the inst
Tiejun Chen wrote:
> When kprobe these operations such as store-and-update-word for SP(r1),
>
> stwu r1, -A(r1)
>
> The program exception is triggered, and PPC always allocate an exception frame
> as shown as the follows:
>
> old r1 --
> ...
> nip
> gpr[2] ~ gp
Hi Linus !
I almost forgot to send you these two patches I had around for some time
now. They fix a nasty warning at boot (and possibly more) when booting a
kernel with CONFIG_PPC_PSERIES enabled on a non-pseries machine.
The first patch just moves a duplicate #define to a common header file,
the
On Mon, 11 Jul 2011 15:41:35 -0500
Yoder Stuart-B08248 wrote:
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Monday, July 11, 2011 1:05 PM
> >
> > Just because Linux does it that way now doesn't mean it needs to. The
> > interrupt controller
> > has a compatible property.
> -Original Message-
> From: Wood Scott-B07421
> Sent: Monday, July 11, 2011 1:05 PM
> To: Yoder Stuart-B08248
> Cc: Wood Scott-B07421; Tabi Timur-B04825; Grant Likely; Benjamin
> Herrenschmidt; Gala Kumar-
> B11780; Alexander Graf; linuxppc-...@ozlabs.org
> Subject: Re: RFC: top level c
On Tue, 12 Jul 2011 04:59:33 +0900
Grant Likely wrote:
> However, compatible values are cheap and while theoretically any
> hypervisor could create a similar machine, the reality is probably
> subtle difference between the implementations. I'd rather see the
> compatible reflect the specific imp
On Mon, Jul 11, 2011 at 11:34 PM, Yoder Stuart-B08248
wrote:
>
>
>> -Original Message-
>> From: Tabi Timur-B04825
>> Sent: Friday, July 08, 2011 8:39 PM
>> To: Yoder Stuart-B08248
>> Cc: Grant Likely; Benjamin Herrenschmidt; Gala Kumar-B11780; Wood
>> Scott-B07421; Alexander
>> Graf; linu
On Sun, 10 Jul 2011 20:55:32 +0200
Fabio Baltieri wrote:
> Change the string to check for CAMP mode boot on MPC85xx (eg. P2020) to match
> the one in the corresponding dts files (p2020rdb_camp_core{0,1}.dts).
>
> Without this fix the mpic is configured as in the SMP boot mode, which causes
> the
On Mon, 11 Jul 2011 12:41:20 -0500
Yoder Stuart-B08248 wrote:
>
>
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Monday, July 11, 2011 11:24 AM
> > To: Tabi Timur-B04825
> > Cc: Yoder Stuart-B08248; Grant Likely; Benjamin Herrenschmidt; Gala
> > Kumar-B11780; Wood Scott-
Scott Wood wrote:
> The device tree is supposed to describe the hardware (virtual or
> otherwise), not just supply what Linux wants. Perhaps there simply
> shouldn't be a toplevel compatible if there's nothing appropriate to
> describe there -- and fix whatever issues Linux has with that.
That mi
> -Original Message-
> From: Wood Scott-B07421
> Sent: Monday, July 11, 2011 11:24 AM
> To: Tabi Timur-B04825
> Cc: Yoder Stuart-B08248; Grant Likely; Benjamin Herrenschmidt; Gala
> Kumar-B11780; Wood Scott-
> B07421; Alexander Graf; linuxppc-...@ozlabs.org
> Subject: Re: RFC: top level
On Mon, 11 Jul 2011 10:45:47 -0500
Timur Tabi wrote:
> >> Also, if these are KVM creations, shouldn't there be a "kvm" in the
> >> compatible string
> >> somewhere?
> >
> > There is nothing KVM specific about these platforms. Any hypervisor
> > could create a similar virtual machine.
>
> True
Yoder Stuart-B08248 wrote:
> We're talking about what would be meaningful to Linux as a guest on
> this platform here-- Corenet-based SoCs are similar
> in various ways, like using msgsnd for IPIs, having external proxy
> support, etc.
>
> A corenet platform created by a QEMU/KVM looks similar
On Tue, Jul 5, 2011 at 3:58 PM, Matthew L. Creech wrote:
>
> Separately, I set up 2 test devices to run while I was away last week.
> One of them contained 2 patches:
>
> - Mike Hench's patch which eliminates this block of code in fsl_elbc_nand.c
> - Adam Thomson's patch
> (http://lists.infradead
> Ok, I'm not familiar with that PIC. You need to check what's going on
> between the PIC, your interrupt source and the kernel.
>
> Normally, if it's an edge interrupt, it's a single event that gets
> latched by the PIC. The kernel will then call ack() on that PIC driver
> (irq_chip) which shoul
> -Original Message-
> From: glik...@secretlab.ca [mailto:glik...@secretlab.ca] On Behalf Of Grant
> Likely
> Sent: Friday, July 08, 2011 9:42 PM
> To: Tabi Timur-B04825
> Cc: Yoder Stuart-B08248; Grant Likely; Benjamin Herrenschmidt; Gala
> Kumar-B11780; Wood Scott-
> B07421; Alexander
> -Original Message-
> From: Tabi Timur-B04825
> Sent: Friday, July 08, 2011 8:39 PM
> To: Yoder Stuart-B08248
> Cc: Grant Likely; Benjamin Herrenschmidt; Gala Kumar-B11780; Wood
> Scott-B07421; Alexander
> Graf; linuxppc-...@ozlabs.org
> Subject: Re: RFC: top level compatibles for virtu
When kprobe these operations such as store-and-update-word for SP(r1),
stwu r1, -A(r1)
The program exception is triggered, and PPC always allocate an exception frame
as shown as the follows:
old r1 --
...
nip
gpr[2] ~ gpr[31]
gpr[1] <- old r1 i
v1 -> v2: when allocate pgirq_ctx, use 'hw_cpu' to identify cpu ID in
exc_lvl_early_init().
v2 -> v3: add that specific return-from-program-exc to restore necessary thread
info then
we can withdraw the original patch #2.
Tiejun
___
Linuxppc-dev mailing
PPC32 ELF ABI expects r2 to be loaded with Thread Pointer, which is 0x7000
bytes past the end of TCB. Though the purgatory is single threaded, it uses
TCB scratch space in vsnprintf(). This patch allocates a 1024byte TCB
and populates the TP with the address accordingly.
Signed-off-by: Suzuki K.
tiejun.chen wrote:
> Ananth N Mavinakayanahalli wrote:
>> On Mon, Jul 11, 2011 at 10:39:35AM +0800, Tiejun Chen wrote:
>>> When enable CONFIG_PREEMPT we will trigger the following call trace:
>>>
>>> BUG: scheduling while atomic: swapper/1/0x1000
>>> ...
>>>
>>> krpobe always goes through the f
Ananth N Mavinakayanahalli wrote:
> On Mon, Jul 11, 2011 at 10:39:35AM +0800, Tiejun Chen wrote:
>> When enable CONFIG_PREEMPT we will trigger the following call trace:
>>
>> BUG: scheduling while atomic: swapper/1/0x1000
>> ...
>>
>> krpobe always goes through the following path:
>>
>> program
Hi Eric,
On 25/06/11 17:49, Eric Dumazet wrote:
> Le samedi 25 juin 2011 à 09:33 +0200, Andreas Schwab a écrit :
>> Matt Evans writes:
>>
>>> + stdur1, -128(r1); \
>>
>>> + addir5, r1, 128+BPF_PPC_STACK_BASIC+(2*8); \
>>
>>> + addir1, r
28 matches
Mail list logo
