On 06.11.20 09:25, Nikhil Devshatwar wrote:
On 17:57-20201030, 'Nikhil Devshatwar' via Jailhouse wrote:
Current PVU iommu implementation ignores possible failures in the
config_commit part. This would allow inconsistent configuration
to run and may introduce unknown bugs.
Solve this by making sure that the pvu_iommu_config_commit never
fails. Catch the errors early in the mapping phase. Use
"free_tlb_count" to track available no of TLBs for chaining.
This can be used to check if any mapping causes it to potentially
use more no of TLBs than that are free. This will ensure that
the allocationg for chaining will not fail.
Change the return type to void for few functions. Add comments to
explain behavior in case of failure. Remove un necessary checks
that would never trigger.
Signed-off-by: Nikhil Devshatwar <[email protected]>
ping on this
Sorry, long backlog. I'll try to work through the Jailhouse patch
backlog soon, latest on Monday.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/f702ebf0-991a-c793-1a3a-dc1f03e2bc9d%40siemens.com.