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

Status information for ECC memory #178

Open
wirthjohannes opened this issue Apr 17, 2020 · 2 comments
Open

Status information for ECC memory #178

wirthjohannes opened this issue Apr 17, 2020 · 2 comments
Assignees

Comments

@wirthjohannes
Copy link
Collaborator

There is currently no easy way to check status information for ECC memory (e.g. is ECC enabled? did ECC errors occur?).

Besides this an easy way to configure ECC online (disable ECC decoding; reset ECC error counter) would also be nice.

Any comments where a good place for this would be?
My suggestion would be in tapasco-debug, either on the "Monitor blue infrastructure" page or on a new "ECC memory" page.

@wirthjohannes wirthjohannes self-assigned this Apr 17, 2020
@jahofmann
Copy link
Contributor

jahofmann commented Apr 17, 2020

tapasco-debug sounds good and we can put a fitting flag to notify the host of ECC capabilities into the status core.

I'm building supporting infrastructure for things like this in the new runtime. Maybe we should wait till this is ready before changing the status core twice.

@wirthjohannes
Copy link
Collaborator Author

Ok, then I'll wait for the new runtime

@wirthjohannes wirthjohannes added this to the 2020.10 milestone Apr 28, 2020
@wirthjohannes wirthjohannes modified the milestones: 2020.10, 2021.4 Oct 23, 2020
@wirthjohannes wirthjohannes modified the milestones: 2021.4, 2021.10 Mar 31, 2021
@cahz cahz modified the milestones: 2022.1, 2022.2 May 17, 2022
@cahz cahz removed this from the 2024.1 milestone Apr 15, 2024
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

No branches or pull requests

3 participants