Implement a proc-macros threads creation #83
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
Implement a proc macro that allows a declaration like:
```rust
fn mythread(arg: usize, arg2: &'static Thing) { .. }
```
With this change, creation of threads, with arbitrary "Send" arguments
can be done without needing allocation. The macros reserves a static
area alongside the `k_thread` structure to use for handing the threads
over.
This creates a function `mythread` with the given args that returns a
ReadyThread. This has a `start()` method which will begin execution of
the thread. This results in a RunningThread, which has a join method
that can be used to wait for termination.
Signed-off-by: David Brown <[email protected]>
Move away from the `kobj_define` task declaration to use the new `#[zephyr::thread]` to define these. This allows for a more natural declaration where the thread just looks like an attribute added to a regular function declaration. This also eliminates the static Mutex, as the Mutex now has a constructor that avoids allocation (it is still put in an Arc, though). Signed-off-by: David Brown <[email protected]>
To help with debugging, try to give created Zephyr threads a readable name. Currently, this is based off of the name of the function used in the declaration of the thread. Signed-off-by: David Brown <[email protected]>
cfriedt
reviewed
Apr 18, 2025
| /// | ||
| /// Will block until the thread has terminated. | ||
| /// | ||
| /// TODO: Allow a timeout? |
There was a problem hiding this comment.
It would be smart to allow a timeout and return the integer result.
There was a problem hiding this comment.
Actually, would it make more sense to do something similar to what std::thread does where we return a Result that can be either Ok or an Err? I guess that's more "rustonic" than integer return values 😅
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.
Replace how Zephyr threads are declared in Rust. Provides a proc-macro to make this fairly straightforward:
This function can then be called, and will return a
ReadThread. This has methods for setting priority, and astartmethod, which returns aRunningThread, which has a join method. The thread can be respawned after it has exited.The thread macro also accepts a
pool_size = nnnparameter, which will create an array of threads, and can be started that many times.