Example for how to do PCI interrupt-line shared interrupts without MSIs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation, operating-systems
Research direction
Start with issue #600 and the shared-interrupt discussion quoted here to understand the PCI interrupt-line pattern and why an intermediary protection domain is needed. Identify the appropriate documentation location, then add a concrete example showing the pattern without MSIs; done means the example explains how the interrupt is routed to the correct device domain.
Written by the indexing model from the issue text.
Description
Even if the kernel allowed it, you still can't tell which PD the interrupt is for, you need device knowledge for that, which requires either broadcast or some driver-level knowledge: so to replicate it on seL4 you need an intermediary PD.
(Possibly we should document this pattern somewhere?)
Originally posted by @midnightveil in https://github.com/seL4/microkit/issues/600#issuecomment-5674264518
- Dominant language
- Rust
- Stars
- 201
- Forks
- 80
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from seL4/microkit
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100