-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved bcm2836/7 IRQ handling #6359
Open
P33M
wants to merge
6
commits into
raspberrypi:rpi-6.6.y
Choose a base branch
from
P33M:armv8_fiq
base: rpi-6.6.y
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Interrupts are dispatched round-robin but doing so trampled FIQ routing. Taking a FIQ on a core without a handler installed is fatal. Only modify bits 1:0 which are the IRQ route bits. Signed-off-by: Jonathan Bell <[email protected]>
BCM2836 with Cortex-A7 cores has almost the same ARM_LOCAL interrupt routing logic as BCM2837, so relax the compile guard to CONFIG_SMP not CONFIG_ARM64. Signed-off-by: Jonathan Bell <[email protected]>
Also declare as static inline, as they should be. Signed-off-by: Jonathan Bell <[email protected]>
The ARM64 architecture uses qspinlock which has a fast and slow path. This isn't ideal for all claimers of a lock operating in interrupt context. Add a ticket-based lock similar to the armv6/7 implementation. Based on an upstream patch that was abandoned in favour of qspinlock. Link: https://patchwork.kernel.org/project/linux-arm-kernel/patch/[email protected]/ Signed-off-by: Jonathan Bell <[email protected]>
Warning on normal behaviour isn't sensible and is spammy. Demote to info. Signed-off-by: Jonathan Bell <[email protected]>
The local spinlock protects the handlers from racing against each other on separate cores, hard IRQs don't preempt each other, and disabling/enabling the interrupt is more expensive than letting the fake FIQ contend the spinlock. So turn local_fiq_en/disable into no-ops. Signed-off-by: Jonathan Bell <[email protected]>
This is exciting! I imagine this might help with the |
At this stage it's more likely to just permute the set of errors you get. There's no guaranteed maximum interrupt latency with this patch series. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First phase of preparing to add platform FIQ support for armv8. Catch some low-hanging fruit first.
Posting as a PR to get autobuilds for all affected platforms (Pi 0 through 3). Only merge if you're feeling brave...