Skip to content

[PW_SID:962953] irqchip/riscv-imsic: Start local sync timer on correct CPU#416

Closed
linux-riscv-bot wants to merge 1 commit into
workflow__riscv__fixesfrom
pw962953
Closed

[PW_SID:962953] irqchip/riscv-imsic: Start local sync timer on correct CPU#416
linux-riscv-bot wants to merge 1 commit into
workflow__riscv__fixesfrom
pw962953

Conversation

@linux-riscv-bot
Copy link
Copy Markdown

PR for series 962953 applied to workflow__riscv__fixes

Name: irqchip/riscv-imsic: Start local sync timer on correct CPU
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=962953
Version: 1

When starting the local sync timer to synchronize the state of a remote
CPU it should be added on the CPU to be synchronized, not the initiating
CPU. This results in interrupt delivery being delayed until the timer
eventually runs (due to another mask/unmask/migrate operation) on the
target CPU.

Fixes: 0f67911 ("irqchip/riscv-imsic: Separate next and previous pointers in IMSIC vector")
Signed-off-by: Andrew Bresticker <abrestic@rivosinc.com>
Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 112.76 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 985.95 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1280.52 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 21.79 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 23.55 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 0.71 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 68.11 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.23 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
kdoc
Desc: Detects for kdoc errors
Duration: 0.90 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.27 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "irqchip/riscv-imsic: Start local sync timer on correct CPU"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.30 seconds
Result: PASS

@linux-riscv-bot linux-riscv-bot deleted the pw962953 branch May 22, 2025 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants