Re: [PATCH v4 4/7] mm: make alloc_contig_range work at pageblock granularity

2022-02-04 Thread Zi Yan
On 4 Feb 2022, at 8:56, Oscar Salvador wrote: > On Wed, Jan 19, 2022 at 02:06:20PM -0500, Zi Yan wrote: >> From: Zi Yan >> >> alloc_contig_range() worked at MAX_ORDER-1 granularity to avoid merging >> pageblocks with different migratetypes. It might unnecessarily convert >> extra pageblocks at

[Bug 215169] UBSAN: shift-out-of-bounds in arch/powerpc/mm/kasan/book3s_32.c:22:23

2022-02-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215169 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

Re: [PATCH v4 4/7] mm: make alloc_contig_range work at pageblock granularity

2022-02-04 Thread Oscar Salvador
On Wed, Jan 19, 2022 at 02:06:20PM -0500, Zi Yan wrote: > From: Zi Yan > > alloc_contig_range() worked at MAX_ORDER-1 granularity to avoid merging > pageblocks with different migratetypes. It might unnecessarily convert > extra pageblocks at the beginning and at the end of the range. Change >

[Bug 214867] UBSAN: shift-out-of-bounds in drivers/of/unittest.c:1933:36

2022-02-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214867 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 215567] New: build failure when PPC_64S_HASH_MMU=n is selected in kernel .config

2022-02-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215567 Bug ID: 215567 Summary: build failure when PPC_64S_HASH_MMU=n is selected in kernel .config Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.17-rc2

[PATCH] powerpc/mm: Update default hugetlb size early

2022-02-04 Thread Aneesh Kumar K.V
We use the default hugetlb page size to calculate pageblock order. set_pageblock_order happens early in the boot and we need to make sure we set the default hugetlb page size before that to compute the right pageblock_order value. arch_initcalls get called later in the boot as shown below

Re: [PATCH 1/2] powerpc/signal: Fix handling of SA_RESTORER sigaction flag

2022-02-04 Thread Christophe Leroy
Le 04/02/2022 à 11:22, Michael Ellerman a écrit : > Christophe Leroy writes: >> powerpc advertises support of SA_RESTORER sigaction flag. >> >> Make it the truth. >> >> Cc: sta...@vger.kernel.org >> Signed-off-by: Christophe Leroy >> --- >> arch/powerpc/kernel/signal_32.c | 8 ++-- >>

Re: [PATCH 1/2] powerpc/signal: Fix handling of SA_RESTORER sigaction flag

2022-02-04 Thread Michael Ellerman
Christophe Leroy writes: > powerpc advertises support of SA_RESTORER sigaction flag. > > Make it the truth. > > Cc: sta...@vger.kernel.org > Signed-off-by: Christophe Leroy > --- > arch/powerpc/kernel/signal_32.c | 8 ++-- > arch/powerpc/kernel/signal_64.c | 4 +++- > 2 files changed, 9

Re: [PATCH] powerpc: Fix xmon ml command to work with 64 bit values.

2022-02-04 Thread Christophe Leroy
Le 25/11/2015 à 00:16, Rashmica Gupta a écrit : The ml command in xmon currently only works for 32-bit values and so fails to find 64-bit values on a ppc64 machine. So change to work for 64-bit values. This is based off a patch by Josh Boyer. Signed-off-by: Rashmica Gupta --- Based off

Re: powerpc: Set crashkernel offset to mid of RMA region

2022-02-04 Thread Sourabh Jain
On 03/02/22 16:37, Michael Ellerman wrote: Sourabh Jain writes: On 01/02/22 17:14, Michael Ellerman wrote: Sourabh Jain writes: On large config LPARs (having 192 and more cores), Linux fails to boot due to insufficient memory in the first memblock. It is due to the memory reservation for

Re: powerpc: Set crashkernel offset to mid of RMA region

2022-02-04 Thread Sourabh Jain
On 01/02/22 16:40, Hari Bathini wrote: On 28/01/22 3:34 pm, Sourabh Jain wrote: On large config LPARs (having 192 and more cores), Linux fails to boot due to insufficient memory in the first memblock. It is due to the memory reservation for the crash kernel which starts at 128MB offset of

powerpc: Set crashkernel offset to mid of RMA region

2022-02-04 Thread Sourabh Jain
On large config LPARs (having 192 and more cores), Linux fails to boot due to insufficient memory in the first memblock. It is due to the memory reservation for the crash kernel which starts at 128MB offset of the first memblock. This memory reservation for the crash kernel doesn't leave enough