-
Notifications
You must be signed in to change notification settings - Fork 0
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
Floating point support #53
Comments
@CharlyCst According to the specification: "The FS[1:0] and VS[1:0] WARL fields and the XS[1:0] read-only field are used to reduce the cost of context save and restore by setting and tracking the current state of the floating-point unit and any other user-mode extensions respectively." |
@CharlyCst Any oppositions if I grab this feature this week? |
As discussed we should look into that when we dig into policy modules. |
@CharlyCst I link this issue to my PR for the protect Payload policy as we also tackle this problem at the same time. |
For now we just ignore floating point registers, but we should ensure they are not leaking from the S-mode payload to the firmware.
I don't know much about the RISC-V implementation yet, but for other architectures there is a dirty bit that says if the floating point registers were accessed. If RISC-V has a similar concept, we should save the floating point registers before transitioning from the payload to the firmware, or from the payload to the firmware.
The text was updated successfully, but these errors were encountered: