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

libcxl doesn't handle a mmio read of 0xfffffff... (all 1's) correctly #20

Open
fbarrat opened this issue Jan 5, 2017 · 2 comments
Open

Comments

@fbarrat
Copy link
Contributor

fbarrat commented Jan 5, 2017

cxl_mmio_read32() and cxl_mmio_read64() consider it an error if a mmio read returns 0xfffffff... (all 1's).
By default when reading 0xffffff, it raises SIGBUS, which terminates the process.

Instead, libcxl should consider 0xffffff... as a hint that an error might have occurred and run extra checks to know for sure. It is similar to what the kernel is doing. The issue is how to do it from userland.

@fbarrat
Copy link
Contributor Author

fbarrat commented Jan 5, 2017

Until it is fixed, AFU won't be able to return 0xffffff.... (all 1's) to a mmio request.

@vaibhav92
Copy link
Contributor

Pull req #25 has been opened with a possible fix for this issue

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

2 participants