[PATCH v10 5/5] MAINTAINERS: objpool added

objpool, a scalable and lockless ring-array based object pool, was introduced to replace the original freelist (a LIFO queue based on singly linked list) to improve kretprobe scalability. Signed-off-by: wuqiang.matt --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git

[PATCH v10 4/5] kprobes: freelist.h removed

This patch will remove freelist.h from kernel source tree, since the only use cases (kretprobe and rethook) are converted to objpool. Signed-off-by: wuqiang.matt --- include/linux/freelist.h | 129 --- 1 file changed, 129 deletions(-) delete mode 100644

[PATCH v10 3/5] kprobes: kretprobe scalability improvement with objpool

kretprobe is using freelist to manage return-instances, but freelist, as LIFO queue based on singly linked list, scales badly and reduces the overall throughput of kretprobed routines, especially for high contention scenarios. Here's a typical throughput test of sys_prctl (counts in 10 seconds,

[PATCH v10 2/5] lib: objpool test module added

The test_objpool module (test_objpool) will run several testcases for objpool stress and performance evaluation. Each testcase will have all available cpu cores involved to create a situation of high parallel and high contention. As of now there are 5 groups and 5 * 2 testcases in total: 1)

[PATCH v10 1/5] lib: objpool added: ring-array based lockless MPMC

objpool is a scalable implementation of high performance queue for object allocation and reclamation, such as kretprobe instances. With leveraging percpu ring-array to mitigate hot spots of memory contention, it delivers near-linear scalability for high parallel scenarios. The objpool is best

[PATCH v10 0/5] lib,kprobes: kretprobe scalability improvement

This patch series introduces a scalable and lockless ring-array based object pool to improve scalability of kretprobed routines. v10: *) objpool simplified and improved according to Masami's advices wuqiang.matt (5): lib: objpool added: ring-array based lockless MPMC lib: objpool test

Re: set_thread_area.2: csky architecture undocumented

Hi Guo, On Tue, Nov 24, 2020 at 08:07:07PM +0800, Guo Ren wrote: Huh, 3 years already! I've had this in my head for all this time; just didn't find the energy to act on it. > Thx Michael & Alejandro, > > Yes, the man page has no csky's. I've applied a patch to add initial documentation for

[RESEND PATCH v3 2/2] remoteproc: enhance rproc_put() for clusters

This patch enhances rproc_put() to support remoteproc clusters with multiple child nodes as in rproc_get_by_phandle(). Reported-by: kernel test robot Link: https://lore.kernel.org/oe-kbuild-all/202303221441.cubnpvye-...@intel.com/ Signed-off-by: Tarak Reddy Signed-off-by: Tanmay Shah ---

[RESEND PATCH v3 0/2] remoteproc: get rproc devices for clusters

This series extends original patch and makes rproc_put() work for clusters along with rprog_get_by_phandle(). Changes in v3: - remove module_put call that was introduced in the patch by mistake - remove redundant check in rproc_put - Add inline comments in rproc_put that explains

[RESEND PATCH v3 1/2] remoteproc: Make rproc_get_by_phandle() work for clusters

From: Mathieu Poirier Multi-cluster remoteproc designs typically have the following DT declaration: remoteproc_cluster { compatible = "soc,remoteproc-cluster"; core0: core0 { compatible = "soc,remoteproc-core"

Re: [PATCH 4/4] arm64: dts: qcom: qcm6490-fairphone-fp5: Add PM7325 thermals

On Samstag, 14. Oktober 2023 01:13:29 CEST Konrad Dybcio wrote: > On 13.10.2023 10:09, Luca Weiss wrote: > > Configure the thermals for the QUIET_THERM, CAM_FLASH_THERM, MSM_THERM > > and RFC_CAM_THERM thermistors connected to PM7325. > > > > With this PMIC the software communication to the ADC

Re: [PATCH 1/4] iio: adc: Add PM7325 PMIC7 ADC bindings

On Fri, 13 Oct 2023 10:09:53 +0200 Luca Weiss wrote: > Add the defines for the ADC channels found on the PM7325. The list is > taken from downstream msm-5.4 and adjusted for mainline. > > Signed-off-by: Luca Weiss I assume this will go with the dts changes that use it. Acked-by: Jonathan

[PATCH v2 1/2] kbuild: unify vdso_install rules

Currently, there is no standard implementation for vdso_install, leading to various issues: 1. Code duplication Many architectures duplicate similar code just for copying files to the install destination. Some architectures (arm, sparc, x86) create build-id symlinks,

[PATCH v2 2/2] kbuild: unify no-compiler-targets and no-sync-config-targets

Now that vdso_install does not depend on any in-tree build artifact, it no longer needs a compiler, making no-compiler-targets the same as no-sync-config-targets. Signed-off-by: Masahiro Yamada --- Changes in v2: - Revive need-compiler flag Makefile | 13 ++--- 1 file changed, 2

Re: [PATCH v2] ACPI: NFIT: Fix local use of devm_*()

On Sat, Oct 14, 2023 at 12:20 AM Dan Williams wrote: > Wilczynski, Michal wrote: ... > "The new cleanup.h facilities that arrived in v6.5-rc1 can replace the > the usage of devm semantics in acpi_nfit_init_interleave_set(). That > routine appears to only be using devm to avoid goto statements.

Re: [PATCH 1/5] csky: remove unused cmd_vdso_install

On Tue, Oct 10, 2023 at 12:16 AM Guo Ren wrote: > > On Mon, Oct 9, 2023 at 8:42 PM Masahiro Yamada wrote: > > > > You cannot run this code because arch/csky/Makefile does not define the > > vdso_install target. > > > > It appears that this code was blindly copied from another architecture. >

Re: [PATCH 5/5] kbuild: unify no-compiler-targets and no-sync-config-targets

On Tue, Oct 10, 2023 at 1:44 AM Nathan Chancellor wrote: > > On Mon, Oct 09, 2023 at 09:42:10PM +0900, Masahiro Yamada wrote: > > Now that vdso_install does not depend on any in-tree build artifact, > > it no longer invokes a compiler, making no-compiler-targets the same > > as