delay during PD initialization and execution

Open
#39 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
networking, operating-systems

Research direction

Start with source/portable/NetworkInterface/xilinx_ultrascale/NetworkInterface.c and locate the vTaskDelay() calls described in the issue. Compare those requirements with sel4cp's event-driven PD model and the proposed timer pp_call approach; done requires a decided, documented mechanism rather than an implementation target currently specified.

Written by the indexing model from the issue text.

Description

Hello!

I am porting an existing network driver code to sel4cp, and the driver has a couple of vTaskDelay() calls (it is for FreeRTOS).

Is there a recommended way of handling such case - e.g. I need my PD to suspend for a short time before continuing in execution?

I can think of the following options:

  1. refactor the code so it fits the event driven paradigm of sel4cp (effectively a state machine) - not practical, the state machine size could get out of hand rather quickly
  2. use pp_call to a timer to get current system time, and busy wait until the desired time elapses - rather inefficient
  3. something else?

@Ivan-Velickovic @nspin

Dominant language
Rust
Stars
201
Forks
80
Avg merge
1d 4h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seL4/microkit

All issues in seL4/microkit

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.