Re: [PATCH] hugetlb: allow to free gigantic pages regardless of the configuration

2019-01-19 Thread Will Deacon
On Thu, Jan 17, 2019 at 06:39:53PM +, Alexandre Ghiti wrote: > From: Alexandre Ghiti > > On systems without CMA or (MEMORY_ISOLATION && COMPACTION) activated but > that support gigantic pages, boottime reserved gigantic pages can not be > freed at all. This patchs simply enables the possibili

Re: [PATCH v13 00/10] powerpc: Switch to CONFIG_THREAD_INFO_IN_TASK

2019-01-19 Thread LEROY Christophe
Michael Ellerman a écrit : Christophe Leroy writes: The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK which moves the thread_info into task_struct. Moving thread_info into task_struct has the following advantages: - It protects thread_info from corruption in the case of st

Re: [PATCH v2] powerpc: chrp: Use device_type helpers to access the node type

2019-01-19 Thread Rob Herring
On Sat, Jan 19, 2019 at 10:18 AM Guenter Roeck wrote: > > The node type can no longer be accessed directly, resulting in the > following build error. Use accessor function instead. > > arch/powerpc/platforms/chrp/setup.c: In function ‘chrp_init_IRQ’: > arch/powerpc/platforms/chrp/setup.c:541:33: e

[PATCH v2] powerpc: chrp: Use device_type helpers to access the node type

2019-01-19 Thread Guenter Roeck
The node type can no longer be accessed directly, resulting in the following build error. Use accessor function instead. arch/powerpc/platforms/chrp/setup.c: In function ‘chrp_init_IRQ’: arch/powerpc/platforms/chrp/setup.c:541:33: error: ‘struct device_node’ has no member named ‘type’ Fix

[PATCH] powerpc: chrp: Use device_type helpers to access the node type

2019-01-19 Thread Guenter Roeck
The node type can no longer be accessed directly, resulting in the following build error. Use accessor function instead. arch/powerpc/platforms/chrp/setup.c: In function ‘chrp_init_IRQ’: arch/powerpc/platforms/chrp/setup.c:541:33: error: ‘struct device_node’ has no member named ‘type’ Fix

Re: [PATCH v2 29/29] y2038: add 64-bit time_t syscalls to all 32-bit architectures

2019-01-19 Thread Russell King - ARM Linux admin
On Fri, Jan 18, 2019 at 11:53:25AM -0800, Andy Lutomirski wrote: > On Fri, Jan 18, 2019 at 11:33 AM Arnd Bergmann wrote: > > > > On Fri, Jan 18, 2019 at 7:50 PM Andy Lutomirski wrote: > > > On Fri, Jan 18, 2019 at 8:25 AM Arnd Bergmann wrote: > > > > - Once we get to 512, we clash with the x32 n

Re: use generic DMA mapping code in powerpc V4

2019-01-19 Thread Christoph Hellwig
On Sat, Jan 19, 2019 at 02:02:22PM +0100, Christoph Hellwig wrote: > Interesting. This suggest it is related to the use of ZONE_DMA by > the FSL SOCs that your board uses. Let me investigate this a bit more. As a hack to check that theory I've pushed a new commit to the powerpc-dma.6-debug branc

Re: use generic DMA mapping code in powerpc V4

2019-01-19 Thread Christoph Hellwig
On Sat, Jan 19, 2019 at 12:52:52PM +0100, Christian Zigotzky wrote: > Hi Christoph, > > I have found a small workaround. If I add 'mem=3500M' to the boot arguments > then it detects the SATA hard disk and boots without any problems. > > X5000> setenv bootargs root=/dev/sda2 console=ttyS0,115200 me

Re: [PATCH] dmaengine: fsldma: Add 64-bit I/O accessors for powerpc64

2019-01-19 Thread Vinod Koul
On 24-12-18, 05:29, Peng Ma wrote: > Hi Scott, > > Oh, I did not see the in_XX64/out_XX64 supported only __powerpc64__ just now. > Thanks for your reminder. Can you send the formal patch for this... FWIW, fsl patches were not merged last cycle because of reported regression... > > #ifdef __pow

Re: use generic DMA mapping code in powerpc V4

2019-01-19 Thread Christian Zigotzky
Hi Christoph, I have found a small workaround. If I add 'mem=3500M' to the boot arguments then it detects the SATA hard disk and boots without any problems. X5000> setenv bootargs root=/dev/sda2 console=ttyS0,115200 mem=3500M Cheers, Christian On 19 January 2019 at 12:40PM, Christian Zigotz

Re: use generic DMA mapping code in powerpc V4

2019-01-19 Thread Christian Zigotzky
Hi Christoph, I bought a USB null modem RS-232 serial cable today so I was able to get some SATA error messages. Error messages: [   13.468538] fsl-sata ffe22.sata: Sata FSL Platform/CSB Driver init [   13.475106] fsl-sata ffe22.sata: failed to start port 0 (errno=-12) [   13.481736]

Re: [PATCH] powerpc: chrp: Use of_node_is_type to access device_type

2019-01-19 Thread Michael Ellerman
Rob Herring writes: > Commit 8ce5f8415753 ("of: Remove struct device_node.type pointer") > removed struct device_node.type pointer, but the conversion to use > of_node_is_type() accessor was missed in chrp_init_IRQ(). > > Fixes: 8ce5f8415753 ("of: Remove struct device_node.type pointer") > Reporte

Re: [PATCH 4/4] powerpc/64s: Support shrinking the SLB for debugging

2019-01-19 Thread Michael Ellerman
Michal Suchánek writes: > On Thu, 17 Jan 2019 23:13:28 +1100 > Michael Ellerman wrote: > >> On machines with 1TB segments and a 32-entry SLB it's quite hard to >> cause sufficient SLB pressure to trigger bugs caused due to badly >> timed SLB faults. >> >> We have seen this in the past and a few

Re: [PATCH v13 00/10] powerpc: Switch to CONFIG_THREAD_INFO_IN_TASK

2019-01-19 Thread Michael Ellerman
Christophe Leroy writes: > The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK which > moves the thread_info into task_struct. > > Moving thread_info into task_struct has the following advantages: > - It protects thread_info from corruption in the case of stack > overflows. > - It