On Sat, Dec 28, 2013 at 1:05 PM, Olof Johansson wrote:
> Sigh, it's not this after all. I did a clean build with this applied
> and still see failures. Something else is (also?) going on here.
Ok, so after some more digging I actually think that this isn't about
the new code added as much as it
Benjamin Herrenschmidt writes:
> On Thu, 2014-01-02 at 16:22 +0530, Aneesh Kumar K.V wrote:
>> > Just use config option directly:
>> >
>> > if (new_ptl != old_ptl ||
>> > IS_ENABLED(CONFIG_ARCH_THP_MOVE_PMD_ALWAYS_WITHDRAW))
>>
>>
>> I didn't like that. I found the earlier o
On Mon, 2013-12-30 at 14:13 +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2013-12-19 at 08:42 +0400, Nikita Yushchenko wrote:
> > No, this does not help.
> >
> > I've dumped the actual content of 'range' and 'addr' at the failure
> > point
> > (i.e. ar point that returns error with e38c0a1f but
This fixes a build break that was probably introduced with the removal
of -Wa,-me500 (commit f49596a4cf4753d13951608f24f939a59fdcc653), where
the assembler refuses to recognize SPRG4-7 with a generic PPC target.
Signed-off-by: Scott Wood
Cc: Dongsheng Wang
Cc: Anton Vorontsov
---
Dongsheng, ple
On Jan 2, 2014, at 12:21 PM, Kumar Gala wrote:
>
> On Dec 31, 2013, at 2:35 PM, jeclark2006 wrote:
>
>> As the subject says... where to post problems with ppc & linux that does not
>> involve 'apple' implementations.
>>
>> The 'embedded' list appears to be pretty much dead.
>
> This is now
On 01/02/2014 11:46 AM, Geoff Levand wrote:
> On Mon, 2013-12-30 at 10:07 +0100, Geert Uytterhoeven wrote:
>> The ps3vram driver is a plain block device driver since commit
>> f507cd22035fdadd5dbb476dd05e9e7ee21c3b84 ("ps3/block: Replace mtd/ps3vram
>> by block/ps3vram").
>>
>> Signed-off-by: Geert
On Dec 31, 2013, at 2:35 PM, jeclark2006 wrote:
> As the subject says... where to post problems with ppc & linux that does not
> involve 'apple' implementations.
>
> The 'embedded' list appears to be pretty much dead.
This is now the list for any ppc linux issues for embedded, server, etc.
-
On Mon, 2013-12-30 at 10:07 +0100, Geert Uytterhoeven wrote:
> The ps3vram driver is a plain block device driver since commit
> f507cd22035fdadd5dbb476dd05e9e7ee21c3b84 ("ps3/block: Replace mtd/ps3vram
> by block/ps3vram").
>
> Signed-off-by: Geert Uytterhoeven
> ---
> drivers/block/ps3vram.c |
On Thu, 2014-01-02 at 16:22 +0530, Aneesh Kumar K.V wrote:
> > Just use config option directly:
> >
> > if (new_ptl != old_ptl ||
> > IS_ENABLED(CONFIG_ARCH_THP_MOVE_PMD_ALWAYS_WITHDRAW))
>
>
> I didn't like that. I found the earlier one easier for reading.
> If you and others
At present we assume candidate image is <= 256MB. But in P8,
candidate image size can go up to 750MB. Hence increasing
candidate image max size to 1GB.
Signed-off-by: Vasant Hegde
---
arch/powerpc/platforms/powernv/opal-flash.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -
"Kirill A. Shutemov" writes:
> Aneesh Kumar K.V wrote:
>> From: "Aneesh Kumar K.V"
>>
>> This patch fix the below crash
>>
>> NIP [c004cee4] .__hash_page_thp+0x2a4/0x440
>> LR [c00439ac] .hash_page+0x18c/0x5e0
>> ...
>> Call Trace:
>> [c00736103c40] [1b00] 0x1ff
Aneesh Kumar K.V wrote:
> From: "Aneesh Kumar K.V"
>
> This patch fix the below crash
>
> NIP [c004cee4] .__hash_page_thp+0x2a4/0x440
> LR [c00439ac] .hash_page+0x18c/0x5e0
> ...
> Call Trace:
> [c00736103c40] [1b00] 0x1b00(unreliable)
> [437908.479693] [c
From: "Aneesh Kumar K.V"
This patch fix the below crash
NIP [c004cee4] .__hash_page_thp+0x2a4/0x440
LR [c00439ac] .hash_page+0x18c/0x5e0
...
Call Trace:
[c00736103c40] [1b00] 0x1b00(unreliable)
[437908.479693] [c00736103d50] [c00439ac] .hash_pa
13 matches
Mail list logo
