Re: [RESEND v2 0/7] Rid W=1 warnings in Ethernet

Hello: This series was applied to netdev/net-next.git (refs/heads/master): On Fri, 15 Jan 2021 20:08:58 + you wrote: > Resending the stragglers again. > This set is part of a larger effort attempting to clean-up W=1 > kernel builds, which are currently overwhelmingly riddled with > niggly lit

Re: [PATCH] Adds a new ioctl32 syscall for backwards compatibility layers

On Fri, Jan 15, 2021 at 11:17:09PM +0100, Arnd Bergmann wrote: > On Fri, Jan 15, 2021 at 9:01 PM David Laight wrote: > > > > From: sonicadvan...@gmail.com > > > Sent: 15 January 2021 07:03 > > > Problem presented: > > > A backwards compatibility layer that allows running x86-64 and x86 > > > proce

RE: [PATCH] Adds a new ioctl32 syscall for backwards compatibility layers

... > He's already doing the system call emulation for all the system > calls other than ioctl in user space though. In my experience, > there are actually fairly few ioctl commands that are different > between architectures -- most of them have no misaligned > or architecture-defined struct member

Re: [PATCH] Adds a new ioctl32 syscall for backwards compatibility layers

On Fri, Jan 15, 2021 at 9:01 PM David Laight wrote: > > From: sonicadvan...@gmail.com > > Sent: 15 January 2021 07:03 > > Problem presented: > > A backwards compatibility layer that allows running x86-64 and x86 > > processes inside of an AArch64 process. > > - CPU is emulated > > - Syscall in

RE: [PATCH] Adds a new ioctl32 syscall for backwards compatibility layers

From: sonicadvan...@gmail.com > Sent: 15 January 2021 07:03 > Problem presented: > A backwards compatibility layer that allows running x86-64 and x86 > processes inside of an AArch64 process. > - CPU is emulated > - Syscall interface is mostly passthrough > - Some syscalls require patching or

Re: CONFIG_PPC_VAS depends on 64k pages...?

Hi all, any news on this matter? Can a patch be submitted for evaluation? Thanks, Carlos On Wed, Dec 2, 2020 at 4:19 AM Will Springer wrote: > On Tuesday, December 1, 2020 5:16:51 AM PST Bulent Abali wrote: > > I don't know anything about VAS page size requirements in the kernel. I > > checke

Re: [PATCH v2] powerpc: Handle .text.{hot,unlikely}.* in linker script

On Sat, Jan 16, 2021 at 12:44:38PM -0600, Segher Boessenkool wrote: > Hi! > > Very late of course, and the patch is fine, but: > > On Mon, Jan 04, 2021 at 01:59:53PM -0700, Nathan Chancellor wrote: > > Commit eff8728fe698 ("vmlinux.lds.h: Add PGO and AutoFDO input > > sections") added ".text.unli

Re: [PATCH v2] powerpc: Handle .text.{hot, unlikely}.* in linker script

Hi! Very late of course, and the patch is fine, but: On Mon, Jan 04, 2021 at 01:59:53PM -0700, Nathan Chancellor wrote: > Commit eff8728fe698 ("vmlinux.lds.h: Add PGO and AutoFDO input > sections") added ".text.unlikely.*" and ".text.hot.*" due to an LLVM > change [1]. > > After another LLVM cha

Re: [PATCH v6 01/39] KVM: PPC: Book3S HV: Context tracking exit guest context before enabling irqs

Excerpts from Nicholas Piggin's message of January 16, 2021 2:49 am: > Interrupts that occur in kernel mode expect that context tracking > is set to kernel. Enabling local irqs before context tracking > switches from guest to host means interrupts can come in and trigger > warnings about wrong cont

Re: [PATCH v6 17/39] powerpc/fsl_booke/32: CacheLockingException remove args

Excerpts from Christophe Leroy's message of January 16, 2021 5:38 pm: > > > Le 16/01/2021 à 01:43, Nicholas Piggin a écrit : >> Excerpts from Christophe Leroy's message of January 16, 2021 3:14 am: >>> >>> >>> Le 15/01/2021 à 17:49, Nicholas Piggin a écrit : Like other interrupt handler conv