Re: [PATCH v3 1/5] arch,locking/atomic: arc: arch_cmpxchg should check data size

2023-11-22 Thread wuqiang.matt
Hello Andi, On 2023/11/23 06:17, Andi Shyti wrote: Hi Wuqiang, On Tue, Nov 21, 2023 at 10:23:43PM +0800, wuqiang.matt wrote: arch_cmpxchg() should check data size rather than pointer size in case CONFIG_ARC_HAS_LLSC is defined. So rename __cmpxchg to __cmpxchg_32 to emphasize it's explicit

Re: [PATCH 0/4] eventfs: Some more minor fixes

2023-11-22 Thread Steven Rostedt
On Wed, 22 Nov 2023 09:19:25 -0500 Josef Bacik wrote: > On Tue, Nov 21, 2023 at 06:10:03PM -0500, Steven Rostedt wrote: > > Mark Rutland reported some crashes from the latest eventfs updates. > > This fixes most of them. > > > > He still has one splat that he can trigger but I can not. Still

Re: [PATCH v2 01/33] ftrace: Unpoison ftrace_regs in ftrace_ops_list_func()

2023-11-22 Thread Steven Rostedt
On Tue, 21 Nov 2023 23:00:55 +0100 Ilya Leoshkevich wrote: > Architectures use assembly code to initialize ftrace_regs and call > ftrace_ops_list_func(). Therefore, from the KMSAN's point of view, > ftrace_regs is poisoned on ftrace_ops_list_func entry(). This causes > KMSAN warnings when

[PATCH 0/4] Section alignment issues?

2023-11-22 Thread deller
From: Helge Deller While working on the 64-bit parisc kernel, I noticed that the __ksymtab[] table was not correctly 64-bit aligned in many modules. The following patches do fix some of those issues in the generic code. But further investigation shows that multiple sections in the kernel and in

[PATCH 3/4] vmlinux.lds.h: Fix alignment for __ksymtab*, __kcrctab_* and .pci_fixup sections

2023-11-22 Thread deller
From: Helge Deller On 64-bit architectures without CONFIG_HAVE_ARCH_PREL32_RELOCATIONS (e.g. ppc64, ppc64le, parisc, s390x,...) the __KSYM_REF() macro stores 64-bit pointers into the __ksymtab* sections. Make sure that the start of those sections is 64-bit aligned in the vmlinux executable,

[PATCH 4/4] modules: Add missing entry for __ex_table

2023-11-22 Thread deller
From: Helge Deller The entry for __ex_table was missing, which may make __ex_table become 1- or 2-byte aligned in modules. Add the entry to ensure it gets 32-bit aligned. Signed-off-by: Helge Deller Cc: # v6.0+ --- scripts/module.lds.S | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 2/4] modules: Ensure 64-bit alignment on __ksymtab_* sections

2023-11-22 Thread deller
From: Helge Deller On 64-bit architectures without CONFIG_HAVE_ARCH_PREL32_RELOCATIONS (e.g. ppc64, ppc64le, parisc, s390x,...) the __KSYM_REF() macro stores 64-bit pointers into the __ksymtab* sections. Make sure that those sections will be correctly aligned at module link time, otherwise

[PATCH 1/4] linux/export: Fix alignment for 64-bit ksymtab entries

2023-11-22 Thread deller
From: Helge Deller An alignment of 4 bytes is wrong for 64-bit platforms which don't define CONFIG_HAVE_ARCH_PREL32_RELOCATIONS (which then store 64-bit pointers). Fix their alignment to 8 bytes. Signed-off-by: Helge Deller --- include/linux/export-internal.h | 5 - 1 file changed, 4

Re: [PATCH v3 1/5] arch,locking/atomic: arc: arch_cmpxchg should check data size

2023-11-22 Thread Andi Shyti
Hi Wuqiang, On Tue, Nov 21, 2023 at 10:23:43PM +0800, wuqiang.matt wrote: > arch_cmpxchg() should check data size rather than pointer size in case > CONFIG_ARC_HAS_LLSC is defined. So rename __cmpxchg to __cmpxchg_32 to > emphasize it's explicit support of 32bit data size with BUILD_BUG_ON() >

Re: [PATCH v2] trace: tracing_event_filter: fast path when no subsystem filters

2023-11-22 Thread Steven Rostedt
On Thu, 12 Oct 2023 16:37:35 -0400 Nick Lowell wrote: Sorry, I was traveling when this was sent, and I missed it. > I really appreciate the continued feedback. I was able to reproduce. > I think I'm understanding better but still need some help. > I am actually wondering if

Re: [PATCH v2 0/5] MODVERSIONS + RUST Redux

2023-11-22 Thread Matthew Maurer
> So, even if you enable CONFIG_MODVERSIONS, > nothing is checked for Rust. > Genksyms computes a CRC from "int foo", and > the module subsystem confirms it is a "int" > variable. > > We know this check always succeeds. > > Why is this useful? The reason this is immediately useful is that it

Re: [PATCH v7 3/4] remoteproc: zynqmp: add pm domains support

2023-11-22 Thread Tanmay Shah
Hi Mathieu, Please find my comments below. On 11/21/23 4:59 PM, Mathieu Poirier wrote: > Hi, > > On Fri, Nov 17, 2023 at 09:42:37AM -0800, Tanmay Shah wrote: > > Use TCM pm domains extracted from device-tree > > to power on/off TCM using general pm domain framework. > > > > Signed-off-by:

Re: [PATCH v7 4/4] remoteproc: zynqmp: parse TCM from device tree

2023-11-22 Thread Mathieu Poirier
On Wed, Nov 22, 2023 at 10:51:08AM -0700, Mathieu Poirier wrote: > On Fri, Nov 17, 2023 at 09:42:38AM -0800, Tanmay Shah wrote: > > ZynqMP TCM information is fixed in driver. Now ZynqMP TCM information > > is available in device-tree. Parse TCM information in driver > > as per new bindings. > > >

[RFC PATCH v3 3/3] vsock/test: SO_RCVLOWAT + deferred credit update test

2023-11-22 Thread Arseniy Krasnov
Test which checks, that updating SO_RCVLOWAT value also sends credit update message. Otherwise mutual hungup may happen when receiver didn't send credit update and then calls 'poll()' with non default SO_RCVLOWAT value (e.g. waiting enough bytes to read), while sender waits for free space at

[RFC PATCH v3 1/3] vsock: update SO_RCVLOWAT setting callback

2023-11-22 Thread Arseniy Krasnov
Do not return if transport callback for SO_RCVLOWAT is set (only in error case). In this case we don't need to set 'sk_rcvlowat' field in each transport - only in 'vsock_set_rcvlowat()'. Signed-off-by: Arseniy Krasnov --- net/vmw_vsock/af_vsock.c | 9 +++-- 1 file changed, 7 insertions(+),

[RFC PATCH v3 0/3] send credit update during setting SO_RCVLOWAT

2023-11-22 Thread Arseniy Krasnov
Hello, DESCRIPTION This patchset fixes old problem with hungup of both rx/tx sides and adds test for it. This happens due to non-default SO_RCVLOWAT value and deferred credit update in virtio/vsock. Link to previous old patchset:

[RFC PATCH v3 2/3] virtio/vsock: send credit update during setting SO_RCVLOWAT

2023-11-22 Thread Arseniy Krasnov
Send credit update message when SO_RCVLOWAT is updated and it is bigger than number of bytes in rx queue. It is needed, because 'poll()' will wait until number of bytes in rx queue will be not smaller than SO_RCVLOWAT, so kick sender to send more data. Otherwise mutual hungup for tx/rx is

Re: [PATCH v7 4/4] remoteproc: zynqmp: parse TCM from device tree

2023-11-22 Thread Mathieu Poirier
On Fri, Nov 17, 2023 at 09:42:38AM -0800, Tanmay Shah wrote: > ZynqMP TCM information is fixed in driver. Now ZynqMP TCM information > is available in device-tree. Parse TCM information in driver > as per new bindings. > > Signed-off-by: Tanmay Shah > --- > > Changes in v7: > - move checking

Re: [PATCH v7 3/4] remoteproc: zynqmp: add pm domains support

2023-11-22 Thread Mathieu Poirier
On Fri, Nov 17, 2023 at 09:42:37AM -0800, Tanmay Shah wrote: > Use TCM pm domains extracted from device-tree > to power on/off TCM using general pm domain framework. > > Signed-off-by: Tanmay Shah > --- > > Changes in v7: > - %s/pm_dev1/pm_dev_core0/r > - %s/pm_dev_link1/pm_dev_core0_link/r

RE: [PATCH v3 4/5] arch,locking/atomic: hexagon: add arch_cmpxchg[64]_local

2023-11-22 Thread Brian Cain
> -Original Message- > From: wuqiang.matt > Sent: Tuesday, November 21, 2023 8:24 AM > To: ubiz...@gmail.com; mark.rutl...@arm.com; vgu...@kernel.org; Brian > Cain ; jo...@southpole.se; > stefan.kristians...@saunalahti.fi; sho...@gmail.com; ch...@zankel.net; > jcmvb...@gmail.com;

Re: [PATCH v2 0/5] MODVERSIONS + RUST Redux

2023-11-22 Thread Masahiro Yamada
On Sat, Nov 18, 2023 at 11:58 AM Matthew Maurer wrote: > > The goal of this patch series is to allow MODVERSIONS and RUST to be > enabled simultaneously. The primary issue with doing this at the moment > is that Rust uses some extremely long symbol names - for those > unfamiliar with Rust, it may

Re: selftests: ftrace: WARNING: __list_del_entry_valid_or_report (lib/list_debug.c:62 (discriminator 1))

2023-11-22 Thread Steven Rostedt
On Wed, 22 Nov 2023 19:49:43 +0530 Naresh Kamboju wrote: > Hi Steven, > > > > On Tue, 21 Nov 2023 at 02:06, Steven Rostedt wrote: > > > > On Thu, 16 Nov 2023 18:00:16 +0530 > > Naresh Kamboju wrote: > > > > > Following kernel crash noticed while running selftests: ftrace on arm64 > > >

Re: [PATCH v2 2/3] arm64: dts: qcom: sc7280: Move video-firmware to chrome-common

2023-11-22 Thread Luca Weiss
On Wed Nov 22, 2023 at 2:17 PM CET, Vikash Garodia wrote: > > On 10/2/2023 7:50 PM, Luca Weiss wrote: > > If the video-firmware node is present, the venus driver assumes we're on > > a system that doesn't use TZ for starting venus, like on ChromeOS > > devices. > > > > Move the video-firmware

Re: selftests: ftrace: WARNING: __list_del_entry_valid_or_report (lib/list_debug.c:62 (discriminator 1))

2023-11-22 Thread Naresh Kamboju
Hi Steven, On Tue, 21 Nov 2023 at 02:06, Steven Rostedt wrote: > > On Thu, 16 Nov 2023 18:00:16 +0530 > Naresh Kamboju wrote: > > > Following kernel crash noticed while running selftests: ftrace on arm64 > > Juno-r2 > > device running stable-rc linux-6.6.y kernel. > > > > This kernel crash

Re: [PATCH 0/4] eventfs: Some more minor fixes

2023-11-22 Thread Josef Bacik
On Tue, Nov 21, 2023 at 06:10:03PM -0500, Steven Rostedt wrote: > Mark Rutland reported some crashes from the latest eventfs updates. > This fixes most of them. > > He still has one splat that he can trigger but I can not. Still looking > into that. Reviewed-by: Josef Bacik Thanks, Josef

Re: [ANNOUNCE] 5.10.201-rt98

2023-11-22 Thread Luis Claudio R. Goncalves
On Tue, Nov 21, 2023 at 10:01:25PM -0300, Luis Claudio R. Goncalves wrote: > Hello RT-list! > > I'm pleased to announce the 5.10.201-rt98 stable release. > > This release is just an update to the new stable 5.10.201 > version and no RT changes have been made. > > You can get this release via

Re: [PATCH v2 3/3] arm64: dts: qcom: qcm6490-fairphone-fp5: Enable venus node

2023-11-22 Thread Vikash Garodia
On 10/2/2023 7:50 PM, Luca Weiss wrote: > Enable the venus node so that the video encoder/decoder will start > working. > > Reviewed-by: Konrad Dybcio > Reviewed-by: Bryan O'Donoghue > Signed-off-by: Luca Weiss > --- > arch/arm64/boot/dts/qcom/qcm6490-fairphone-fp5.dts | 5 + > 1 file

Re: [PATCH v2 2/3] arm64: dts: qcom: sc7280: Move video-firmware to chrome-common

2023-11-22 Thread Vikash Garodia
On 10/2/2023 7:50 PM, Luca Weiss wrote: > If the video-firmware node is present, the venus driver assumes we're on > a system that doesn't use TZ for starting venus, like on ChromeOS > devices. > > Move the video-firmware node to chrome-common.dtsi so we can use venus > on a non-ChromeOS

Re: [PATCH v2 1/3] media: venus: core: Set up secure memory ranges for SC7280

2023-11-22 Thread Vikash Garodia
On 10/2/2023 7:50 PM, Luca Weiss wrote: > Not all SC7280 devices ship with ChromeOS firmware. Other devices need > PAS for image authentication. That requires the predefined virtual > address ranges to be passed via scm calls. Define them to enable Venus > on non-CrOS SC7280 devices. > >

Re: Re: EEVDF/vhost regression (bisected to 86bfbb7ce4f6 sched/fair: Add lag based placement)

2023-11-22 Thread Peter Zijlstra
On Tue, Nov 21, 2023 at 02:17:21PM +0100, Tobias Huschle wrote: > We applied both suggested patch options and ran the test again, so > > sched/eevdf: Fix vruntime adjustment on reweight > sched/fair: Update min_vruntime for reweight_entity() correctly > > and > > sched/eevdf: Delay dequeue >

Re: [PATCH RFC v2 20/27] mm: hugepage: Handle huge page fault on access

2023-11-22 Thread Alexandru Elisei
Hi Peter, On Tue, Nov 21, 2023 at 05:28:49PM -0800, Peter Collingbourne wrote: > On Sun, Nov 19, 2023 at 8:59 AM Alexandru Elisei > wrote: > > > > Handle PAGE_FAULT_ON_ACCESS faults for huge pages in a similar way to > > regular pages. > > > > Signed-off-by: Alexandru Elisei > > --- > >

Re: [PATCH net v1] vsock/test: fix SEQPACKET message bounds test

2023-11-22 Thread Stefano Garzarella
On Wed, Nov 22, 2023 at 12:16:42AM +0300, Arseniy Krasnov wrote: Tune message length calculation to make this test work on machines where 'getpagesize()' returns >32KB. Now maximum message length is not hardcoded (on machines above it was smaller than 'getpagesize()' return value, thus we get