Re: [PATCH] MAINTAINERS: Remove myself as EEH maintainer

2022-08-10 Thread Michael Ellerman
Russell Currey writes: > I haven't touched EEH in a long time I don't have much knowledge of the > subsystem at this point either, so it's misleading to have me as a > maintainer. Thank you for your service. > I remain grateful to Oliver for picking up my slack over the years. Ack. But I wonde

[powerpc:fixes-test] BUILD SUCCESS 83ee9f23763a432a4077bf20624ee35de87bce99

2022-08-10 Thread kernel test robot
randconfig-a012 x86_64randconfig-a014 x86_64randconfig-a016 hexagon randconfig-r045-20220810 hexagon randconfig-r041-20220810 i386 randconfig-a002 i386 randconfig-a006 i386

Re: [PATCH v2 13/14] powerpc/64s: Fix comment on interrupt handler prologue

2022-08-10 Thread Rohan McLure
> Maybe it would be interesting to know from which patch the error comes. It’s hard to attribute this to a single commit, but the distance between r10’s save location and r11-r12’s save location has definitely grown over time. The comment is introduced in commit 7180e3e636de ("[POWERPC] force 64

Re: [PATCH v2] powerpc/kexec: Fix build failure from uninitialised variable

2022-08-10 Thread Nathan Chancellor
On Wed, Aug 10, 2022 at 03:43:31PM +1000, Russell Currey wrote: > clang 14 won't build because ret is uninitialised and can be returned if > both prop and fdtprop are NULL. Drop the ret variable and return an > error in that failure case. > > Fixes: b1fc44eaa9ba ("pseries/iommu/ddw: Fix kdump to

Re: [PATCHv3, resend] powerpc: mm: radix_tlb: rearrange the if-else block

2022-08-10 Thread Segher Boessenkool
Hi! On Wed, Aug 10, 2022 at 01:43:18PM +0200, Anders Roxell wrote: > Clang warns: > > arch/powerpc/mm/book3s64/radix_tlb.c:1191:23: error: variable 'hstart' is > uninitialized when used here [-Werror,-Wuninitialized] > __tlbiel_va_range(hstart, hend, pid, >

[PATCHv3, resend] powerpc: mm: radix_tlb: rearrange the if-else block

2022-08-10 Thread Anders Roxell
Clang warns: arch/powerpc/mm/book3s64/radix_tlb.c:1191:23: error: variable 'hstart' is uninitialized when used here [-Werror,-Wuninitialized] __tlbiel_va_range(hstart, hend, pid, ^~ arch/powerpc/mm/book3s64/radi

Re: [PATCH v2 10/14] powerpc: Provide syscall wrapper

2022-08-10 Thread Andrew Donnellan
On Mon, 2022-07-25 at 16:30 +1000, Rohan McLure wrote: > Implement syscall wrapper as per s390, x86, arm64. When enabled > cause handlers to accept parameters from a stack frame rather than > from user scratch register state. This allows for user registers to > be > safely cleared in order to reduc

Re: [PATCH 05/16] powerpc: Skip objtool from running on drivers/crypto/vmx/aesp8-ppc.o

2022-08-10 Thread Christophe Leroy
Le 08/08/2022 à 13:48, Sathvika Vasireddy a écrit : > With objtool enabled, below warnings are seen when trying to build: > > drivers/crypto/vmx/aesp8-ppc.o: warning: objtool: > aes_p8_set_encrypt_key+0x44: unannotated intra-function call > > drivers/crypto/vmx/aesp8-ppc.o: warning: objtool: .

Re: [PATCH 03/16] powerpc: Fix objtool unannotated intra-function call warnings

2022-08-10 Thread Christophe Leroy
Le 08/08/2022 à 13:48, Sathvika Vasireddy a écrit : > objtool throws unannotated intra-function call warnings > in the following assembly files. > > arch/powerpc/kernel/vector.o: warning: objtool: .text+0x53c: unannotated > intra-function call > > arch/powerpc/kvm/book3s_hv_rmhandlers.o: warni

Re: [PATCH 02/16] powerpc: override __ALIGN() and __ALIGN_STR() macros

2022-08-10 Thread Christophe Leroy
Le 08/08/2022 à 13:48, Sathvika Vasireddy a écrit : > Since we need an alignment of 4 bytes, override > __ALIGN() and __ALIGN_STR() accordingly. Why/When do we now need an alignment of 4 bytes ? Please explain the reason in the commit message. > > Signed-off-by: Sathvika Vasireddy > --- >

Re: [PATCH 01/16] powerpc: Replace unreachable() with it's builtin variant in WARN_ON()

2022-08-10 Thread Christophe Leroy
Le 08/08/2022 à 13:48, Sathvika Vasireddy a écrit : > objtool is throwing *unannotated intra-function call* > warnings with a few instructions that are marked > unreachable. Replace unreachable() with __builtin_unreachable() > to fix these warnings, as the codegen remains same > with unreachable(