[PATCH 23/41] openrisc: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers

2025-03-14 Thread Thomas Huth
While the GCC and Clang compilers already define __ASSEMBLER__ automatically when compiling assembly code, __ASSEMBLY__ is a macro that only gets defined by the Makefiles in the kernel. This can be very confusing when switching between userspace and kernelspace coding, or when dealing with uapi hea

[PATCH 2/4] selftests: ntsync: avoid possible overflow in 32-bit machine

2025-03-14 Thread Su Hui
When using '-m32' flag to compile this test with gcc, there are some errors when running test: ntsync.c:785:wake_any:Expected ETIMEDOUT (110) == ret (0) ntsync.c:823:wake_any:Expected (1) (1) == __count (0) ... FAILED: 7 / 11 tests passed. Totals: pass:7 fail:4 xfail:0 xpass:0 skip:0 error:0

[PATCH 1/4] selftests: ntsync: fix the wrong condition in wake_all

2025-03-14 Thread Su Hui
When 'manual=false' and 'signaled=true', then expected value when using NTSYNC_IOC_CREATE_EVENT should be greater than zero. Fix this typo error. Signed-off-by: Su Hui --- tools/testing/selftests/drivers/ntsync/ntsync.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/

[PATCH 3/4] selftests: ntsync: update config

2025-03-14 Thread Su Hui
ntsync should be tested when CONFIG_NTSYNC is setting rather than CONFIG_WINESYNC, correct this. Signed-off-by: Su Hui --- tools/testing/selftests/drivers/ntsync/config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/drivers/ntsync/config b/tools/test

[PATCH 22/41] openrisc: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers

2025-03-14 Thread Thomas Huth
__ASSEMBLY__ is only defined by the Makefile of the kernel, so this is not really useful for uapi headers (unless the userspace Makefile defines it, too). Let's switch to __ASSEMBLER__ which gets set automatically by the compiler when compiling assembly code. This is a completely mechanical patch

Re: [PATCH 1/2] dt-bindings: input: touchscreen: edt-ft5x06: Document FT8716 support

2025-03-14 Thread Krzysztof Kozlowski
On Thu, Mar 13, 2025 at 09:20:16PM +0100, Jens Reidel wrote: > Document FocalTech FT8716 support by adding the compatible. > > Signed-off-by: Jens Reidel > --- > .../devicetree/bindings/input/touchscreen/edt-ft5x06.yaml| 1 + > 1 file changed, 1 insertion(+) Acked-by: Krzysztof Kozlowsk

Re: [PATCH 1/4] selftests: ntsync: fix the wrong condition in wake_all

2025-03-14 Thread Su Hui
On 2025/3/14 18:14, Su Hui wrote: On 2025/3/14 17:21, Dan Carpenter wrote: On Fri, Mar 14, 2025 at 03:14:51PM +0800, Su Hui wrote: When 'manual=false' and 'signaled=true', then expected value when using NTSYNC_IOC_CREATE_EVENT should be greater than zero. Fix this typo error. Signed-off-by:

Re: [PATCH 1/4] selftests: ntsync: fix the wrong condition in wake_all

2025-03-14 Thread Dan Carpenter
On Fri, Mar 14, 2025 at 03:14:51PM +0800, Su Hui wrote: > When 'manual=false' and 'signaled=true', then expected value when using > NTSYNC_IOC_CREATE_EVENT should be greater than zero. Fix this typo error. > > Signed-off-by: Su Hui > --- > tools/testing/selftests/drivers/ntsync/ntsync.c | 2 +-

[PATCH net-next v2] vsock/test: Add test for null ptr deref when transport changes

2025-03-14 Thread Luigi Leonardi
Add a new test to ensure that when the transport changes a null pointer dereference does not occur[1]. Note that this test does not fail, but it may hang on the client side if it triggers a kernel oops. This works by creating a socket, trying to connect to a server, and then executing a second co

Re: [PATCH net-next] selftests: drv-net: fix merge conflicts resolution

2025-03-14 Thread Paolo Abeni
On 3/14/25 9:35 AM, Matthieu Baerts (NGI0) wrote: > After the recent merge between net-next and net, I got some conflicts on > my side because the merge resolution was different from Stephen's one > [1] I applied on my side in the MPTCP tree. > > It looks like the code that is now in net-next is u

[PATCH 2/3] arm64: dts: qcom: sm6350: Add OPP table support to UFSHC

2025-03-14 Thread Luca Weiss
UFS host controller, when scaling gears, should choose appropriate performance state of RPMh power domain controller along with clock frequency. So let's add the OPP table support to specify both clock frequency and RPMh performance states replacing the old "freq-table-hz" property. Signed-off-by:

[PATCH 1/3] arm64: dts: qcom: sm6350: Fix wrong order of freq-table-hz for UFS

2025-03-14 Thread Luca Weiss
During upstreaming the order of clocks was adjusted to match the upstream sort order, but mistakently freq-table-hz wasn't re-ordered with the new order. Fix that by moving the entry for the ICE clk to the last place. Fixes: 5a814af5fc22 ("arm64: dts: qcom: sm6350: Add UFS nodes") Cc: Signed-off

[PATCH 3/3] arm64: dts: qcom: sm6350: Add interconnect support to UFS

2025-03-14 Thread Luca Weiss
Define the two NoC paths used by UFS: ufs-ddr and cpu-ufs. Signed-off-by: Luca Weiss --- arch/arm64/boot/dts/qcom/sm6350.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sm6350.dtsi b/arch/arm64/boot/dts/qcom/sm6350.dtsi index 77ca8990c7a096f40aab5666da9

Re: [PATCH v3 08/10] selftests/mm: Skip gup_longerm tests on weird filesystems

2025-03-14 Thread David Hildenbrand
On 12.03.25 09:34, Brendan Jackman wrote: On Tue, Mar 11, 2025 at 08:53:02PM +0100, David Hildenbrand wrote: 2. 9pfs seems to pass the f_type through from the host. So you can't detect it this way anyway. [3. I guess overlayfs & friends would also be an issue here although that doesn't affect m

Re: [PATCH v9 6/6] scanf: further break kunit into test cases

2025-03-14 Thread Petr Mladek
On Fri 2025-03-07 06:27:39, Tamir Duberstein wrote: > This gives us more granular test output. > > Output before: > > > KTAP version 1 > > 1..1 > > KTAP version 1 > > # Subtest: scanf > > # module: scanf_kunit > > 1..10 > > ok 1 numbers_simple > > KTAP version 1 > >

[PATCH 0/5 v2] rcu/exp updates

2025-03-14 Thread Frederic Weisbecker
Hi, Changes in this version: * [1/5] Explain why it's fine if a task unblocks between sync_exp_reset_tree() and __sync_rcu_exp_select_node_cpus(), per Paul's suggestion. * [3/5] Add Paul's reviewed-by tag * [4/5] and [5/5] are new patches after discussion. Frederic Weisbecker (5): rcu/ex

[PATCH 1/5] rcu/exp: Protect against early QS report

2025-03-14 Thread Frederic Weisbecker
When a grace period is started, the ->expmask of each node is set up from sync_exp_reset_tree(). Then later on each leaf node also initialize its ->exp_tasks pointer. This means that the initialization of the quiescent state of a node and the initialization of its blocking tasks happen with an unl

[PATCH 2/5] rcu/exp: Remove confusing needless full barrier on task unblock

2025-03-14 Thread Frederic Weisbecker
A full memory barrier in the RCU-PREEMPT task unblock path advertizes to order the context switch (or rather the accesses prior to rcu_read_unlock()) with the expedited grace period fastpath. However the grace period can not complete without the rnp calling into rcu_report_exp_rnp() with the node

[PATCH 5/5] rcu/exp: Warn on CPU lagging for too long within hotplug IPI's blindspot

2025-03-14 Thread Frederic Weisbecker
A CPU within hotplug operations can make the RCU exp kworker lagging if: * The dying CPU is running after CPUHP_TEARDOWN_CPU but before rcutree_report_cpu_dead(). It is too late to send an IPI but RCU is still watching the CPU. Therefore the exp kworker can only wait for the target to reach

Re: [PATCH v3 08/10] selftests/mm: Skip gup_longerm tests on weird filesystems

2025-03-14 Thread Brendan Jackman
> > Even if it's a bug in QEMU, I think it is worth working around this > > one way or another. QEMU by far the most practical way to run these > > tests, and virtme-ng is probably the most popular/practical way to do > > that. > > I'm afraid yes. Although allocating temp files form 9pfs is rather

Re: [PATCH] rust: sync: rcu: Mark Guard methods as inline

2025-03-14 Thread Miguel Ojeda
On Thu, Mar 13, 2025 at 5:30 AM Joel Fernandes wrote: > > Reviewed-by: Joel Fernandes > > If no objections, I can queue it for 6.16 but let me know if Rust maintainers > prefer to take it. Thanks! That would be great -- FWIW: Acked-by: Miguel Ojeda By the way, should `read_lock()` be marked t

Re: [PATCH v9 6/6] scanf: further break kunit into test cases

2025-03-14 Thread Tamir Duberstein
On Fri, Mar 14, 2025 at 9:21 AM Petr Mladek wrote: > > Thanks for trying this. But I personally do not find this as a big win. > It causes that the test log is longer than one screen and thus harder > to review. > > It might be fine when running only this test and running it only once. > But I thi

Re: [RFC PATCH] mmc: sdhci-pxav3: set NEED_RSP_BUSY capability

2025-03-14 Thread Adrian Hunter
On 10/03/25 16:07, Karel Balej wrote: > Set the MMC_CAP_NEED_RSP_BUSY capability for the sdhci-pxav3 host to > prevent conversion of R1B responses to R1. Without this, the eMMC card > in the samsung,coreprimevelte smartphone using the Marvell PXA1908 SoC > with this mmc host doesn't probe with the

Re: [PATCH 3/3] rcu/exp: Remove needless CPU up quiescent state report

2025-03-14 Thread Frederic Weisbecker
Le Mon, Mar 03, 2025 at 12:10:50PM -0800, Paul E. McKenney a écrit : > On Fri, Feb 14, 2025 at 12:25:59AM +0100, Frederic Weisbecker wrote: > > A CPU coming online checks for an ongoing grace period and reports > > a quiescent state accordingly if needed. This special treatment that > > shortcuts t

[PATCH 4/5] rcu/exp: Warn on QS requested on dying CPU

2025-03-14 Thread Frederic Weisbecker
It is not possible to send an IPI to a dying CPU that has passed the CPUHP_TEARDOWN_CPU stage. Remaining unhandled IPIs are handled later at CPUHP_AP_SMPCFD_DYING stage by stop machine. This is the last opportunity for RCU exp handler to request an expedited quiescent state. And the upcoming final

[PATCH 3/5] rcu/exp: Remove needless CPU up quiescent state report

2025-03-14 Thread Frederic Weisbecker
A CPU coming online checks for an ongoing grace period and reports a quiescent state accordingly if needed. This special treatment that shortcuts the expedited IPI finds its origin as an optimization purpose on the following commit: 338b0f760e84 (rcu: Better hotplug handling for synchroni

Re: [PATCH v9 4/6] scanf: break kunit into test cases

2025-03-14 Thread Petr Mladek
On Fri 2025-03-07 06:27:37, Tamir Duberstein wrote: > Use `suite_init` and move some tests into `scanf_test_cases`. This > gives us nicer output in the event of a failure. > > Reviewed-by: David Gow > Signed-off-by: Tamir Duberstein Reviewed-by: Petr Mladek Tested-by: Petr Mladek Best Regard

Re: [PATCH 00/13] selftests/bpf: Integrate test_xsk.c to test_progs framework

2025-03-14 Thread Bastien Curutchet
Hi Maciej On 3/14/25 4:45 PM, Maciej Fijalkowski wrote: On Thu, Mar 13, 2025 at 11:47:58AM +0100, Bastien Curutchet (eBPF Foundation) wrote: Hi all, This patch series continues the work to migrate the script tests into prog_tests. Hi Bastien, the sole purpose of this is a cleanup of some s

Re: [PATCH] rust: sync: rcu: Mark Guard methods as inline

2025-03-14 Thread I Hsin Cheng
On Fri, Mar 14, 2025 at 03:43:23PM +0100, Miguel Ojeda wrote: > On Thu, Mar 13, 2025 at 5:30 AM Joel Fernandes wrote: > > > > Reviewed-by: Joel Fernandes > > > > If no objections, I can queue it for 6.16 but let me know if Rust > > maintainers > > prefer to take it. > > Thanks! That would be gr

Re: [PATCH PATCH 2/2] selftests: livepatch: test if ftrace can trace a livepatched function

2025-03-14 Thread Miroslav Benes
Hi, > +start_test "trace livepatched function and check that the live patch remains > in effect" > + > +FUNCTION_NAME="livepatch_cmdline_proc_show" > + > +load_lp $MOD_LIVEPATCH > +trace_function "$FUNCTION_NAME" trace_funtion() calls cleanup_ftrace() to prepare the test. Ok. > +if [[ "$(cat /p

Re: [PATCH v9 0/6] scanf: convert self-test to KUnit

2025-03-14 Thread Petr Mladek
On Fri 2025-03-07 06:27:33, Tamir Duberstein wrote: > This is one of just 3 remaining "Test Module" kselftests (the others > being bitmap and printf), the rest having been converted to KUnit. In > addition to the enclosed patch, please consider this an RFC on the > removal of the "Test Module" ksel

Re: [PATCH v9 5/6] scanf: tidy header `#include`s

2025-03-14 Thread Petr Mladek
On Fri 2025-03-07 06:27:38, Tamir Duberstein wrote: > Remove the unused `kernel.h`. Replace `string.h` with `sprintf.h` as the > former doesn't seem to be used directly. > --- a/lib/tests/scanf_kunit.c > +++ b/lib/tests/scanf_kunit.c > @@ -5,12 +5,11 @@ > > #include > #include > -#include >

Re: [PATCH 00/13] selftests/bpf: Integrate test_xsk.c to test_progs framework

2025-03-14 Thread Maciej Fijalkowski
On Thu, Mar 13, 2025 at 11:47:58AM +0100, Bastien Curutchet (eBPF Foundation) wrote: > Hi all, > > This patch series continues the work to migrate the script tests into > prog_tests. Hi Bastien, the sole purpose of this is a cleanup of some sort? > > The test_xsk.sh script tests lots of AF_XD

[PATCH net v2 3/3] vsock/bpf: Fix bpf recvmsg() racing transport reassignment

2025-03-14 Thread Michal Luczaj
Signal delivery during connect() may lead to a disconnect of an already established socket. That involves removing socket from any sockmap and resetting state to SS_UNCONNECTED. While it correctly restores socket's proto, a call to vsock_bpf_recvmsg() might have been already under way in another th

[PATCH net v2 1/3] vsock/bpf: Fix EINTR connect() racing sockmap update

2025-03-14 Thread Michal Luczaj
Signal delivery during connect() may result in a disconnect of an already TCP_ESTABLISHED socket. Problem is that such established socket might have been placed in a sockmap before the connection was closed. We end up with a SS_UNCONNECTED vsock in a sockmap. And this, combined with the ability to

Re: [PATCH] rust: enable `clippy::ptr_as_ptr` lint

2025-03-14 Thread Miguel Ojeda
On Thu, Mar 13, 2025 at 1:41 AM Philip Li wrote: > > Sorry about this, I will implement this to make it clear asap. The bot is great -- thanks for all the resources you have put so far into it :) Cheers, Miguel

[PATCH net v2 0/3] vsock/bpf: Handle races between sockmap update and connect() disconnecting

2025-03-14 Thread Michal Luczaj
Signal delivery during connect() may disconnect an already established socket. Problem is that such socket might have been placed in a sockmap before the connection was closed. PATCH 1 ensures this race won't lead to an unconnected vsock staying in the sockmap. PATCH 2 selftests it. PATCH 3 fixes

Re: [RFC PATCH 0/5] KVM: guest_memfd: support for uffd missing

2025-03-14 Thread Nikita Kalyazin
On 13/03/2025 22:38, Peter Xu wrote: On Thu, Mar 13, 2025 at 10:13:23PM +, Nikita Kalyazin wrote: Yes, that's right, mmap() + memcpy() is functionally sufficient. write() is an optimisation. Most of the pages in guest_memfd are only ever accessed by the vCPU (not userspace) via TDP (stag

Re: [PATCH v9 0/6] scanf: convert self-test to KUnit

2025-03-14 Thread Tamir Duberstein
On Fri, Mar 14, 2025 at 4:45 PM Kees Cook wrote: > > On Fri, Mar 14, 2025 at 02:29:40PM +0100, Petr Mladek wrote: > > On Fri 2025-03-07 06:27:33, Tamir Duberstein wrote: > > > This is one of just 3 remaining "Test Module" kselftests (the others > > > being bitmap and printf), the rest having been

Re: [PATCH] module: Taint the kernel when write-protecting ro_after_init fails

2025-03-14 Thread Kees Cook
On Fri, Mar 14, 2025 at 05:48:00PM +0100, Christophe Leroy wrote: > > > Le 12/03/2025 à 17:30, Kees Cook a écrit : > > On Wed, Mar 12, 2025 at 04:45:24PM +0100, Vlastimil Babka wrote: > > > On 3/6/25 17:57, Luis Chamberlain wrote: > > > > + linux-mm since we're adding TAINT_BAD_PAGE > > > > > >

Re: [PATCH v9 0/6] scanf: convert self-test to KUnit

2025-03-14 Thread Kees Cook
On Fri, Mar 14, 2025 at 02:29:40PM +0100, Petr Mladek wrote: > On Fri 2025-03-07 06:27:33, Tamir Duberstein wrote: > > This is one of just 3 remaining "Test Module" kselftests (the others > > being bitmap and printf), the rest having been converted to KUnit. In > > addition to the enclosed patch, p

Re: [PATCH v3 08/10] selftests/mm: Skip gup_longerm tests on weird filesystems

2025-03-14 Thread David Hildenbrand
On 14.03.25 16:56, Brendan Jackman wrote: Even if it's a bug in QEMU, I think it is worth working around this one way or another. QEMU by far the most practical way to run these tests, and virtme-ng is probably the most popular/practical way to do that. I'm afraid yes. Although allocating temp

Re: [PATCH v2] arm64: dts: qcom: qcm6490-fairphone-fp5: Add touchscreen node

2025-03-14 Thread Bjorn Andersson
On Wed, 12 Mar 2025 12:14:59 +0100, Luca Weiss wrote: > Add a node for the GT9897 touchscreen found on this smartphone connected > via SPI. > > Applied, thanks! [1/1] arm64: dts: qcom: qcm6490-fairphone-fp5: Add touchscreen node commit: 6c6d55f41c1b54b16d35f16c02fe99cc0ad019e0 Best reg

Re: [PATCH PATCH 2/2] selftests: livepatch: test if ftrace can trace a livepatched function

2025-03-14 Thread Filipe Xavier
On 3/14/25 10:14 AM, Miroslav Benes wrote: Hi, +start_test "trace livepatched function and check that the live patch remains in effect" + +FUNCTION_NAME="livepatch_cmdline_proc_show" + +load_lp $MOD_LIVEPATCH +trace_function "$FUNCTION_NAME" trace_funtion() calls cleanup_ftrace() to prepare

[PATCH] remoteproc: qcom: pas: add minidump_id to SC7280 WPSS

2025-03-14 Thread Luca Weiss
_wpss_resource = { .crash_reason_smem = 626, .firmware_name = "wpss.mdt", .pas_id = 6, + .minidump_id = 4, .auto_boot = false, .proxy_pd_names = (char*[]){ "cx", --- base-commit: eea255893718268e1ab852fb52f70c613d109b

[PATCH net-next] selftests: drv-net: fix merge conflicts resolution

2025-03-14 Thread Matthieu Baerts (NGI0)
,7 +120,7 @@ def get_interface_info(cfg) -> None: global remote_ifname global no_sleep -remote_info = cmd(f"ip -4 -o addr show to {cfg.remote_v4} | awk '{{print $2}}'", shell=True, host=cfg.remote).stdout + remote_info = cmd(f"ip -4 -o addr show to {cfg

Re: [PATCH bpf-next 01/11] bpf: Move insn if/else into do_check_insn()

2025-03-14 Thread Eduard Zingerman
On Thu, 2025-03-13 at 18:21 +0100, Luis Gerhorst wrote: > This is required to catch the errors later and fall back to a nospec if > on a speculative path. > > Move code into do_check_insn(), replace > * "continue" with "return INSN_IDX_MODIFIED" > * "goto process_bpf_exit" with "return PROCESS_BPF

Re: [PATCH 3/3] arm64: dts: qcom: sm6350: Add interconnect support to UFS

2025-03-14 Thread Konrad Dybcio
On 3/14/25 10:17 AM, Luca Weiss wrote: > Define the two NoC paths used by UFS: ufs-ddr and cpu-ufs. > > Signed-off-by: Luca Weiss > --- Reviewed-by: Konrad Dybcio Konrad

Re: [PATCH] remoteproc: imx_dsp_rproc: Document run_stall struct member

2025-03-14 Thread Mathieu Poirier
On Fri, Mar 14, 2025 at 05:17:19PM +0200, Daniel Baluta wrote: > Add documentation for 'run_stall' imx_dsp_rproc struct member. > This also fixes the following warning: > > warning: Function parameter or struct member 'run_stall' > not described in 'imx_dsp_rproc' > > Fixes: 0184b4fdbad1 ("imx_ds

Re: [PATCH] module: Taint the kernel when write-protecting ro_after_init fails

2025-03-14 Thread Christophe Leroy
Le 12/03/2025 à 17:30, Kees Cook a écrit : On Wed, Mar 12, 2025 at 04:45:24PM +0100, Vlastimil Babka wrote: On 3/6/25 17:57, Luis Chamberlain wrote: + linux-mm since we're adding TAINT_BAD_PAGE On Thu, Mar 06, 2025 at 11:36:55AM +0100, Petr Pavlu wrote: In the unlikely case that setting ro

[PATCH net v2 2/3] selftest/bpf: Add test for AF_VSOCK connect() racing sockmap update

2025-03-14 Thread Michal Luczaj
Racing signal-interrupted connect() and sockmap update may result in an unconnected (and missing vsock transport) socket in a sockmap. Test spends 2 seconds attempting to reach WARN_ON_ONCE(). connect / state = SS_CONNECTED / sock_map_update_elem if signal_pend

Re: [RFC] openrisc: Add cacheinfo support

2025-03-14 Thread Sahil Siddiq
Hi, On 3/14/25 2:54 AM, Stafford Horne wrote: On Tue, Mar 11, 2025 at 12:43:57AM +0530, Sahil Siddiq wrote: Add cacheinfo support for OpenRISC. [...] None of the functions in drivers/base/cacheinfo.c that are capable of pulling these details (e.g.: cache_size) have been used. This is because t

Re: [RFC PATCH 0/5] KVM: guest_memfd: support for uffd missing

2025-03-14 Thread Peter Xu
On Fri, Mar 14, 2025 at 05:12:35PM +, Nikita Kalyazin wrote: > Anyway, it looks like the solution we discussed allows to choose between > memcpy-only and memcpy/write-combined userspace implementations. I'm going > to work on the next version of the series that would include MINOR trap and > a

Re: [PATCH 1/3] arm64: dts: qcom: sm6350: Fix wrong order of freq-table-hz for UFS

2025-03-14 Thread Konrad Dybcio
On 3/14/25 10:17 AM, Luca Weiss wrote: > During upstreaming the order of clocks was adjusted to match the > upstream sort order, but mistakently freq-table-hz wasn't re-ordered > with the new order. > > Fix that by moving the entry for the ICE clk to the last place. > > Fixes: 5a814af5fc22 ("arm6

Re: [PATCH 3/4] selftests: ntsync: update config

2025-03-14 Thread Elizabeth Figura
On Friday, 14 March 2025 02:14:53 CDT Su Hui wrote: > ntsync should be tested when CONFIG_NTSYNC is setting rather than > CONFIG_WINESYNC, correct this. > > Signed-off-by: Su Hui > --- > tools/testing/selftests/drivers/ntsync/config | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > di

Re: [RFC] openrisc: Add cacheinfo support

2025-03-14 Thread Stafford Horne
On Sat, Mar 15, 2025 at 01:34:03AM +0530, Sahil Siddiq wrote: > Hi, > > On 3/14/25 2:54 AM, Stafford Horne wrote: > > On Tue, Mar 11, 2025 at 12:43:57AM +0530, Sahil Siddiq wrote: > > > Add cacheinfo support for OpenRISC. > > > > > > [...] > > > None of the functions in drivers/base/cacheinfo.c t

Re: [PATCH 1/4] selftests: ntsync: fix the wrong condition in wake_all

2025-03-14 Thread Elizabeth Figura
On Friday, 14 March 2025 02:14:51 CDT Su Hui wrote: > When 'manual=false' and 'signaled=true', then expected value when using > NTSYNC_IOC_CREATE_EVENT should be greater than zero. Fix this typo error. > > Signed-off-by: Su Hui > --- > tools/testing/selftests/drivers/ntsync/ntsync.c | 2 +- >

Re: [PATCH 1/4] selftests: ntsync: fix the wrong condition in wake_all

2025-03-14 Thread Elizabeth Figura
On Friday, 14 March 2025 05:14:30 CDT Su Hui wrote: > On 2025/3/14 17:21, Dan Carpenter wrote: > > On Fri, Mar 14, 2025 at 03:14:51PM +0800, Su Hui wrote: > >> When 'manual=false' and 'signaled=true', then expected value when using > >> NTSYNC_IOC_CREATE_EVENT should be greater than zero. Fix thi

Re: [PATCH 2/4] selftests: ntsync: avoid possible overflow in 32-bit machine

2025-03-14 Thread Elizabeth Figura
On Friday, 14 March 2025 02:14:52 CDT Su Hui wrote: > When using '-m32' flag to compile this test with gcc, there are some > errors when running test: > > ntsync.c:785:wake_any:Expected ETIMEDOUT (110) == ret (0) > ntsync.c:823:wake_any:Expected (1) (1) == __count (0) > ... > FAILED: 7 / 11 t

Re: (subset) [PATCH v9 0/6] scanf: convert self-test to KUnit

2025-03-14 Thread Kees Cook
On Fri, 07 Mar 2025 06:27:33 -0500, Tamir Duberstein wrote: > This is one of just 3 remaining "Test Module" kselftests (the others > being bitmap and printf), the rest having been converted to KUnit. In > addition to the enclosed patch, please consider this an RFC on the > removal of the "Test Modu

Re: [PATCH 2/3] arm64: dts: qcom: sm6350: Add OPP table support to UFSHC

2025-03-14 Thread Konrad Dybcio
On 3/14/25 10:17 AM, Luca Weiss wrote: > UFS host controller, when scaling gears, should choose appropriate > performance state of RPMh power domain controller along with clock > frequency. So let's add the OPP table support to specify both clock > frequency and RPMh performance states replacing th

[RFC PATCH 2/2] selftests/timers: Improve skew_consistency by testing with other clockids

2025-03-14 Thread John Stultz
Lei Chen reported a bug with CLOCK_MONOTONIC_COARSE having inconsistencies when NTP is adjusting the clock frequency. This has gone seemingly undetected for ~15 years, illustrating a clear gap in our testing. The skew_consistency test is intended to catch this sort of problem, but was focused on

[RFC PATCH 1/2] time/timekeeping: Fix possible inconsistencies in _COARSE clockids

2025-03-14 Thread John Stultz
Lei Chen raised an issue with CLOCK_MONOTONIC_COARSE seeing time inconsistencies. Lei tracked down that this was being caused by the adjustment tk->tkr_mono.xtime_nsec -= offset; which is made to compensate for the unaccumulated cycles in offset when the mult value is adjusted forward, so that

[PATCH RFC 8/8] selftests/sched_ext: Add test for sched_ext dl_server

2025-03-14 Thread Joel Fernandes
From: Andrea Righi Add a selftest to validate the correct behavior of the deadline server for the ext_sched_class. [ Joel: Replaced occurences of CFS in the test with EXT. ] Signed-off-by: Joel Fernandes Signed-off-by: Andrea Righi --- tools/testing/selftests/sched_ext/Makefile| 1 + .