Skip to content
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

docs: add missing software_irq KIPC docs #1965

Merged
merged 4 commits into from
Jan 15, 2025
Merged

Conversation

hawkw
Copy link
Member

@hawkw hawkw commented Dec 26, 2024

I recently discovered that the software_irq KIPC call is missing
reference documentation. In fact, the KIPC documentation doesn't even
mention it (in contrast to other KIPC calls that have no documentation
but are still listed in the reference). Instead, the reference
documentation currently incorrectly states that find_faulted_task is
KIPC number 8, when it's actually KIPC 9 and software_irq is number 8.

Not adding this KIPC to the docs was an oversight on my part in PR #1661
--- my bad, sorry!

This commit adds documentation for the software_irq KIPC to the
reference.

I [recently discovered][1] that the `software_irq` KIPC call is missing
reference documentation. In fact, the KIPC documentation doesn't even
mention it (in contrast to other KIPC calls that have no documentation
but are still listed in the reference). Instead, the reference
documentation currently incorrectly states that `find_faulted_task` is
KIPC number 8, when it's actually KIPC 9 and `software_irq` is number 8.

Not adding this KIPC to the docs was an oversight on my part in PR #1661
--- my bad, sorry!

This commit adds documentation for the `software_irq` KIPC to the
reference.

[1]: #1961 (comment)
@hawkw hawkw self-assigned this Dec 26, 2024
@hawkw hawkw requested a review from cbiffle December 26, 2024 19:22
@hawkw
Copy link
Member Author

hawkw commented Dec 26, 2024

doc/kipc.adoc Outdated

This interface is primarily intended for testing interrupt handling, and can
only be called by a task running as the supervisor. When this KIPC is called,
an actual machine interrupt is triggered and dispatched by the kernel to the
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would split this up to make it more obvious that the KIPC only triggers the interrupt, something like

When this KIPC is called, an actual machine interrupt is triggered for the relevant hardware interrupt source. The kernel then responds to the interrupt using its normal interrupt-handling infrastructure, which dispatches a notification to the subscribed task.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I agree that's nicer.

@hawkw hawkw enabled auto-merge (rebase) January 15, 2025 18:48
@hawkw hawkw merged commit 794bded into master Jan 15, 2025
125 checks passed
@hawkw hawkw deleted the eliza/document-soft-irq branch January 15, 2025 18:56
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