[PW_SID:958645] KVM: lockdep improvements by linux-riscv-bot · Pull Request #360 · linux-riscv/linux

linux-riscv-bot · 2025-04-30T21:19:01Z

PR for series 958645 applied to workflow__riscv__fixes

Name: KVM: lockdep improvements
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=958645
Version: 4

Despite the fact that several lockdep-related checks are skipped when calling trylock* versions of the locking primitives, for example mutex_trylock, each time the mutex is acquired, a held_lock is still placed onto the lockdep stack by __lock_acquire() which is called regardless of whether the trylock* or regular locking API was used. This means that if the caller successfully acquires more than MAX_LOCK_DEPTH locks of the same class, even when using mutex_trylock, lockdep will still complain that the maximum depth of the held lock stack has been reached and disable itself. For example, the following error currently occurs in the ARM version of KVM, once the code tries to lock all vCPUs of a VM configured with more than MAX_LOCK_DEPTH vCPUs, a situation that can easily happen on modern systems, where having more than 48 CPUs is common, and it's also common to run VMs that have vCPU counts approaching that number: [ 328.171264] BUG: MAX_LOCK_DEPTH too low! [ 328.175227] turning off the locking correctness validator. [ 328.180726] Please attach the output of /proc/lock_stat to the bug report [ 328.187531] depth: 48 max: 48! [ 328.190678] 48 locks held by qemu-kvm/11664: [ 328.194957] #0: ffff800086de5ba0 (&kvm->lock){+.+.}-{3:3}, at: kvm_ioctl_create_device+0x174/0x5b0 [ 328.204048] #1: ffff0800e78800b8 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.212521] #2: ffff07ffeee51e98 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.220991] #3: ffff0800dc7d80b8 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.229463] #4: ffff07ffe0c980b8 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.237934] #5: ffff0800a3883c78 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.246405] #6: ffff07fffbe480b8 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 Luckily, in all instances that require locking all vCPUs, the 'kvm->lock' is taken a priori, and that fact makes it possible to use the little known feature of lockdep, called a 'nest_lock', to avoid this warning and subsequent lockdep self-disablement. The action of 'nested lock' being provided to lockdep's lock_acquire(), causes the lockdep to detect that the top of the held lock stack contains a lock of the same class and then increment its reference counter instead of pushing a new held_lock item onto that stack. See __lock_acquire for more information. Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Use mutex_trylock_nest_lock instead of mutex_trylock when locking all vCPUs of a VM, to avoid triggering a lockdep warning, if the VM is configured to have more than MAX_LOCK_DEPTH vCPUs. This fixes the following false lockdep warning: [ 328.171264] BUG: MAX_LOCK_DEPTH too low! [ 328.175227] turning off the locking correctness validator. [ 328.180726] Please attach the output of /proc/lock_stat to the bug report [ 328.187531] depth: 48 max: 48! [ 328.190678] 48 locks held by qemu-kvm/11664: [ 328.194957] #0: ffff800086de5ba0 (&kvm->lock){+.+.}-{3:3}, at: kvm_ioctl_create_device+0x174/0x5b0 [ 328.204048] #1: ffff0800e78800b8 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.212521] #2: ffff07ffeee51e98 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.220991] #3: ffff0800dc7d80b8 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.229463] #4: ffff07ffe0c980b8 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.237934] #5: ffff0800a3883c78 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 [ 328.246405] #6: ffff07fffbe480b8 (&vcpu->mutex){+.+.}-{3:3}, at: lock_all_vcpus+0x16c/0x2a0 Since the locking of all vCPUs is a primitive that can be useful in other architectures that are supported by KVM, also move the code to kvm_main.c Suggested-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Use the kvm_trylock_all_vcpus()/unlock_all_vcpus() instead of riscv's own implementation, to avoid triggering a lockdep warning, if the VM is configured to have more than MAX_LOCK_DEPTH vCPUs. Compile tested only. Suggested-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

KVM's SEV intra-host migration code needs to lock all vCPUs of the source and the target VM, before it proceeds with the migration. The number of vCPUs that belong to each VM is not bounded by anything except a self-imposed KVM limit of CONFIG_KVM_MAX_NR_VCPUS vCPUs which is significantly larger than the depth of lockdep's lock stack. Luckily, the locks in both of the cases mentioned above, are held under the 'kvm->lock' of each VM, which means that we can use the little known lockdep feature called a "nest_lock" to support this use case in a cleaner way, compared to the way it's currently done. Implement and expose 'mutex_lock_killable_nest_lock' for this purpose. Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Implement kvm_lock_all_vcpus() and use it instead of sev own sev_{lock|unlock}_vcpus_for_migration(). Suggested-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot · 2025-04-30T21:24:11Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 104.07 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T21:55:54Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1901.97 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:36:14Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 2418.44 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:36:35Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.05 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:36:58Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.05 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:37:01Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 1.76 seconds
Result: WARNING
Output:

CHECK: extern prototypes should be avoided in .h files
#65: FILE: include/linux/mutex.h:198:
+extern int _mutex_trylock_nest_lock(struct mutex *lock, struct lockdep_map *nest_lock);

WARNING: Argument 'nest_lock' is not used in function-like macro
#76: FILE: include/linux/mutex.h:209:
+#define mutex_trylock_nest_lock(lock, nest_lock) mutex_trylock(lock)

total: 0 errors, 1 warnings, 1 checks, 57 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Commit d78ffbedc736 ("locking/mutex: implement mutex_trylock_nested") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT CAMELCASE COMMIT_LOG_LONG_LINE GIT_COMMIT_ID MACRO_ARG_REUSE NO_AUTHOR_SIGN_OFF

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.
total: 0 errors, 1 warnings, 1 checks, 57 lines checked
CHECK: extern prototypes should be avoided in .h files
WARNING: Argument 'nest_lock' is not used in function-like macro

linux-riscv-bot · 2025-04-30T22:38:09Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 66.15 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:38:10Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.25 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:38:13Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
kdoc
Desc: Detects for kdoc errors
Duration: 0.89 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:38:14Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:38:16Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:38:18Z

Patch 1: "[v4,1/5] locking/mutex: implement mutex_trylock_nested"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.32 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:40:18Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 104.03 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T22:56:35Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 975.49 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:17:34Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1257.44 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:17:55Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.21 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:18:18Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.18 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:18:21Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 2.16 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:19:29Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 66.01 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:19:31Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:19:33Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
kdoc
Desc: Detects for kdoc errors
Duration: 0.92 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:19:35Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
module-param
Desc: Detect module_param changes
Duration: 0.27 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:19:36Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:19:38Z

Patch 2: "[v4,2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.30 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:58:01Z

Patch 3: "[v4,3/5] RISC-V: KVM: switch to kvm_trylock/unlock_all_vcpus"
module-param
Desc: Detect module_param changes
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:58:03Z

Patch 3: "[v4,3/5] RISC-V: KVM: switch to kvm_trylock/unlock_all_vcpus"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2025-04-30T23:58:05Z

Patch 3: "[v4,3/5] RISC-V: KVM: switch to kvm_trylock/unlock_all_vcpus"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.29 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T00:00:05Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 104.77 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T00:31:53Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1906.23 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:12:16Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 2422.14 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:12:38Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.10 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:13:00Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.17 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:13:03Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 1.75 seconds
Result: WARNING
Output:

CHECK: extern prototypes should be avoided in .h files
#41: FILE: include/linux/mutex.h:161:
+extern int __must_check _mutex_lock_killable(struct mutex *lock,

CHECK: Alignment should match open parenthesis
#42: FILE: include/linux/mutex.h:162:
+extern int __must_check _mutex_lock_killable(struct mutex *lock,
+		unsigned int subclass, struct lockdep_map *nest_lock);

WARNING: Argument 'nest_lock' is not used in function-like macro
#72: FILE: include/linux/mutex.h:194:
+# define mutex_lock_killable_nest_lock(lock, nest_lock) mutex_lock_killable(lock)

CHECK: Alignment should match open parenthesis
#86: FILE: kernel/locking/mutex.c:812:
+_mutex_lock_killable(struct mutex *lock, unsigned int subclass,
+				      struct lockdep_map *nest)

total: 0 errors, 1 warnings, 3 checks, 56 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Commit 19af2982d1a5 ("locking/mutex: implement mutex_lock_killable_nest_lock") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT CAMELCASE COMMIT_LOG_LONG_LINE GIT_COMMIT_ID MACRO_ARG_REUSE NO_AUTHOR_SIGN_OFF

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.
total: 0 errors, 1 warnings, 3 checks, 56 lines checked
CHECK: Alignment should match open parenthesis
CHECK: extern prototypes should be avoided in .h files
WARNING: Argument 'nest_lock' is not used in function-like macro

linux-riscv-bot · 2025-05-01T01:14:12Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 66.90 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:14:13Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.25 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:14:16Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
kdoc
Desc: Detects for kdoc errors
Duration: 0.91 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:14:17Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:14:19Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:14:21Z

Patch 4: "[v4,4/5] locking/mutex: implement mutex_lock_killable_nest_lock"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.31 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:16:21Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 104.61 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:32:45Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 982.86 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:53:48Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1261.78 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:54:10Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 19.61 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:54:32Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.05 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:54:35Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 1.15 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:55:42Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 66.28 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:55:44Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.27 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:55:46Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
kdoc
Desc: Detects for kdoc errors
Duration: 0.94 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:55:48Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
module-param
Desc: Detect module_param changes
Duration: 0.27 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:55:50Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.78 seconds
Result: PASS

linux-riscv-bot · 2025-05-01T01:55:52Z

Patch 5: "[v4,5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.31 seconds
Result: PASS

Linux RISC-V bot and others added 6 commits April 30, 2025 11:41

Adding CI files

4d9ad71

linux-riscv-bot force-pushed the workflow__riscv__fixes branch from 4d9ad71 to 625be03 Compare May 6, 2025 09:20

linux-riscv-bot closed this May 7, 2025

linux-riscv-bot deleted the pw958645 branch May 7, 2025 14:20

Conversation

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented Apr 30, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025

Uh oh!

linux-riscv-bot commented May 1, 2025