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

interrupts: efficient user interrupt event push #47

Open
pthierry-ledger opened this issue Sep 24, 2024 · 0 comments
Open

interrupts: efficient user interrupt event push #47

pthierry-ledger opened this issue Sep 24, 2024 · 0 comments
Labels
api impact the external API of the component enhancement request for code evolution
Milestone

Comments

@pthierry-ledger
Copy link
Member

By now, the kernel delivers one interrupt at a time to a userspace task that is requesting waiting interrupt from its queue using the sys_waitforevent() syscall.
Instead, the kernel should be able to delivers at once the complete list of interrupts so that the userspace thread can:

  • get back all interrupt at once with a single system call
  • decide in which order all waiting IRQ can be handled (userspace-local priority decision)

This will highly increase interrupt efficiency & reactivity for projects that manupulate (a lot of-) interrupts. This mostly requires
that the waiting IRQ vector should be pushed to userspace through SVC exhange area, and thus requiring a header that specify the length of the transmitted IRQ vector.

@pthierry-ledger pthierry-ledger added api impact the external API of the component enhancement request for code evolution labels Sep 24, 2024
@pthierry-ledger pthierry-ledger added this to the Sentry-v1.0.0 milestone Sep 24, 2024
@pthierry-ledger pthierry-ledger changed the title interrupt: efficient user interrupt event push interrupts: efficient user interrupt event push Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api impact the external API of the component enhancement request for code evolution
Projects
None yet
Development

No branches or pull requests

1 participant