-
Notifications
You must be signed in to change notification settings - Fork 18
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
Can you clarify "command-queue access" #254
Comments
Yes. It includes both. |
Would be a good clarification to include - see 6902620. |
If the write access failure of IOFENCE.C command with AV=1 will set the cqmf to 1, the cqh will reference the IOFENCE.C command. But a IOFENCE.C command completion is determined by cqh advancing past the index of the IOFENCE.C command in the CQ and the IOMMU writes data to memory with AV=1 when the IOFENCE.C command completes. It seems that there is confusion in the description of the spec. When a write access leads a failure with AV=1, wheather the IOFENCE.C is complete?Using only cqh and cqmf does not seem to be enough; it cannot indicate both IOFENCE.C completion and memory failure. |
The IOFENCE.C is not complete because it encounters a memory fault. |
Thanks for your answer. And could you consider revising the sentence in the spec, as it reads very ambiguously in terms of time relationships?
|
And in the function do_fence_c, the bit fence_w_ip will be set to 1 no matter whether the write access is successful if the AV=1. So is there an error in the c_model? |
Yes, the |
The |
Can you clarify what does "command-queue access" mean in description of cqmf ?
Does it include command queue read access and the write access of IOFENCE.C command with AV=1?
riscv-iommu/iommu_registers.adoc
Lines 782 to 786 in 61026ef
The text was updated successfully, but these errors were encountered: