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

RFC template for nominating CSRs to be write-safe #256

Merged
merged 1 commit into from
Jan 12, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
name: "`riscv`: Nominate CSR to be `write` safe"
about: Suggest to make writes of a given CSR safe
title: "`riscv`: make [CSR] write-safe"
labels: ''
assignees: ''

---

**Which CSR do you want to nominate as `write` safe?**
Indicate which CSR you want to be `write` safe. Ex. `mepc`

**Does a CSR write introduce potential memory safety issues in safe code? Please describe.**
A clear and concise justification on why writing to this CSR will **never** introduce memory safety issues in safe code.

**Does a CSR write introduce potential undefined behavior in safe code? Please describe.**
A clear and concise justification on why writing to this CSR will **never** lead to undefined behavior in safe code.

**Does a CSR write invalidate invariants in safe code?**
A clear and concise justification on why writing to this CSR will **never** invalidate invariants in safe code.

**Additional context**
Please feel free to add any other context or screenshots about your request here.
Loading