Re: KVM: lockdep improvements

[linux.r...@gmail.com]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the Linux RISC-V mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/linux-riscv/list/?series=962152

---Test result---
Test Summary:
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" build-rv32-defconfig PASS 108.28 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" build-rv64-clang-allmodconfig PASS 1943.69 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" build-rv64-gcc-allmodconfig PASS 2464.86 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" build-rv64-nommu-k210-defconfig PASS 21.51 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" build-rv64-nommu-k210-virt PASS 22.61 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" checkpatch WARNING 1.81 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" dtb-warn-rv64 PASS 68.56 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" header-inline PASS 0.34 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" kdoc PASS 0.93 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" module-param PASS 0.26 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" verify-fixes PASS 0.23 seconds
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested" verify-signedoff PASS 0.31 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" build-rv32-defconfig PASS 107.91 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" build-rv64-clang-allmodconfig PASS 1935.97 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" build-rv64-gcc-allmodconfig PASS 2460.10 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" build-rv64-nommu-k210-defconfig PASS 20.64 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" build-rv64-nommu-k210-virt PASS 21.78 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" checkpatch WARNING 2.06 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" dtb-warn-rv64 PASS 68.40 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" header-inline PASS 0.25 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" kdoc PASS 0.92 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" module-param PASS 0.27 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" verify-fixes PASS 0.23 seconds
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock" verify-signedoff PASS 0.31 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" build-rv32-defconfig PASS 106.73 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" build-rv64-clang-allmodconfig PASS 994.43 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" build-rv64-gcc-allmodconfig PASS 1282.36 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" build-rv64-nommu-k210-defconfig PASS 20.90 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" build-rv64-nommu-k210-virt PASS 21.82 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" checkpatch PASS 1.01 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" dtb-warn-rv64 PASS 67.28 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" header-inline PASS 0.67 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" kdoc PASS 0.95 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" module-param PASS 0.27 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" verify-fixes PASS 0.23 seconds
Patch 3: "[v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus" verify-signedoff PASS 0.32 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" build-rv32-defconfig PASS 106.35 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" build-rv64-clang-allmodconfig PASS 889.56 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" build-rv64-gcc-allmodconfig PASS 1155.92 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" build-rv64-nommu-k210-defconfig PASS 20.59 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" build-rv64-nommu-k210-virt PASS 22.47 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" checkpatch PASS 0.74 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" dtb-warn-rv64 PASS 67.52 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" header-inline PASS 2.79 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" kdoc PASS 1.02 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" module-param PASS 0.61 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" verify-fixes PASS 0.22 seconds
Patch 4: "[v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation" verify-signedoff PASS 0.29 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv32-defconfig PASS 106.08 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv64-clang-allmodconfig PASS 889.41 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv64-gcc-allmodconfig PASS 1151.74 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv64-nommu-k210-defconfig PASS 20.70 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv64-nommu-k210-virt PASS 21.93 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" checkpatch PASS 1.76 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" dtb-warn-rv64 PASS 67.24 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" header-inline PASS 0.25 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" kdoc PASS 0.93 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" module-param PASS 0.30 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" verify-fixes PASS 0.23 seconds
Patch 5: "[v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs" verify-signedoff PASS 0.31 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv32-defconfig PASS 106.31 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv64-clang-allmodconfig PASS 911.03 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv64-gcc-allmodconfig PASS 1189.66 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv64-nommu-k210-defconfig PASS 21.02 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" build-rv64-nommu-k210-virt PASS 21.64 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" checkpatch PASS 0.70 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" dtb-warn-rv64 PASS 68.28 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" header-inline PASS 0.24 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" kdoc PASS 0.85 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" module-param PASS 0.26 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" verify-fixes PASS 0.22 seconds
Patch 6: "[v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs" verify-signedoff PASS 0.31 seconds

Details
##############################
Patch 1: "[v5,1/6] locking/mutex: implement mutex_trylock_nested"
Test: checkpatch - WARNING
Desc: Runs checkpatch.pl on the patch
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 1a66b8febd79 ("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


##############################
Patch 2: "[v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock"
Test: checkpatch - WARNING
Desc: Runs checkpatch.pl on the patch
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 627f1a43b81f ("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




---
Regards,
Linux RISC-V bot