-
Notifications
You must be signed in to change notification settings - Fork 3
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
dma: building exchange api #58
Merged
pthierry-ledger
merged 14 commits into
outpost-os:main
from
pthierry-ledger:dma-exchange-api
Oct 1, 2024
Merged
dma: building exchange api #58
pthierry-ledger
merged 14 commits into
outpost-os:main
from
pthierry-ledger:dma-exchange-api
Oct 1, 2024
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
pthierry-ledger
requested review from
iartemov-ledger and
fvalette-ledger
and removed request for
iartemov-ledger
September 30, 2024 08:10
pthierry-ledger
added
api
impact the external API of the component
feature
New feature added
test
test or test suite related
labels
Sep 30, 2024
pthierry-ledger
changed the title
DMA: building exchange api
dma: building exchange api
Sep 30, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1st pass
update autotest to support this new API
I didn't find the auto-test update.
fvalette-ledger
requested changes
Sep 30, 2024
Hem yes 👍 I havent pushed that last commit :) done now. |
preparing DMA event support as new task event
fixing dmas and irqs queue with circular buffer usage
the goal here is to make the task queue support easier and shorter
pthierry-ledger
force-pushed
the
dma-exchange-api
branch
from
October 1, 2024 06:42
f826b05
to
baabb72
Compare
pthierry-ledger
force-pushed
the
dma-exchange-api
branch
from
October 1, 2024 07:51
27e60b8
to
031464b
Compare
fvalette-ledger
approved these changes
Oct 1, 2024
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.
As defined in DMA wiki, adding a new event queue specific to DMA streams vents.
As DMA streams events are specific, consolidated, events types, they should be pushed up to userspace tasks as such, instead of pushing bare IRQn.
Bare IRQn are useless to userspace, as DMA IRQ acknowledge is under the kernel control. Instead pushing consolidated event is useful for user task, as they can directly manipulate such event for functional implementation.
A DMA event is then received as a specific event of the
wait_for_event()
syscall. In that case, the event received looks like the following tuple:This tuple allows to directly associate the handle with a userspace context, and the DMA event type used to react to various events as required.
The DMA event structure pushed by the kernel is the following, respecting the exchange_event_t standard Sentry header:
This allows such a usage:
wait_for_event()
events listwait_for_event()
syscall leveldepends on #44
closes #60