Skip to content

ARM: FPU: implement ASSERT-based testing of multi-usage in Unshared FP Services mode #15292

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

Open
ioannisg opened this issue Apr 9, 2019 · 1 comment
Assignees
Labels
area: ARM ARM (32-bit) Architecture Enhancement Changes/Updates/Additions to existing features
Milestone

Comments

@ioannisg
Copy link
Member

ioannisg commented Apr 9, 2019

We may want to enhance the implementation of Unshared FP Services' mode, by providing a testing mechanism that detects corruptions of FPU as a result of accidental sharing between multiple thread contexts.

The mechanism should trigger ASSERTS if the FPU is used by multiple threads under the Unshared Mode (CONFIG_FLOAT=y, CONFIG_FP_SHARING=n).

@ioannisg ioannisg added the Enhancement Changes/Updates/Additions to existing features label Apr 9, 2019
@ioannisg ioannisg added the area: ARM ARM (32-bit) Architecture label Apr 9, 2019
@ioannisg ioannisg added this to the future milestone Apr 9, 2019
@ioannisg ioannisg changed the title ARM: FPU: imlement ASSERT-based testing of multi-usage in Unshared FP Services mode ARM: FPU: implement ASSERT-based testing of multi-usage in Unshared FP Services mode Apr 9, 2019
@nashif nashif removed this from the future milestone May 21, 2019
@ioannisg ioannisg added this to the v2.1.0 milestone Jul 31, 2019
@dleach02 dleach02 modified the milestones: v2.1.0, v2.2.0 Dec 10, 2019
@ioannisg ioannisg modified the milestones: v2.2.0, v2.3.0 Mar 4, 2020
@carlescufi carlescufi modified the milestones: v2.3.0, v2.4.0 Jun 5, 2020
@zephyrbot
Copy link
Collaborator

Hi @microbuilder, @XenuIsWatching, @stephanosio, @kristofer-jonsson-arm,

This issue, marked as an Enhancement, was opened a while ago and did not get any traction. It was just assigned to you based on the labels. If you don't consider yourself the right person to address this issue, please re-assing it to the right person.

Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.

@ioannisg you are also encouraged to help moving this issue forward by providing additional information and confirming this request/issue is still relevant to you.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ARM ARM (32-bit) Architecture Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

No branches or pull requests