Skip to content
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

Removing xtdc #519

Closed
jrtc27 opened this issue Feb 4, 2025 · 1 comment · Fixed by #527
Closed

Removing xtdc #519

jrtc27 opened this issue Feb 4, 2025 · 1 comment · Fixed by #527

Comments

@jrtc27
Copy link
Collaborator

jrtc27 commented Feb 4, 2025

As discussed in #503, it is believed that xtdc are not in fact required. sscratchc can be used to store whatever capability you need on entry to the kernel, and from there you can have any additional state you need stored. FreeBSD already uses it to store a pointer to per-CPU data when running in userspace, and so in CheriBSD we can extend it to also store DDC for hybrid kernels (implementation at CTSRD-CHERI/cheribsd@2178d40) rather than needing a separate register.

Does anyone have a reason why they believe xtdc should remain in the specification?

@andresag01
Copy link
Collaborator

It would be great to remove them! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants