23 Aug
2017
23 Aug
'17
4:51 p.m.
Hi,
Thank you for detailed explanation.
We understand that emulated interrupt on the frontend side is completely not acceptable and definitely we need to provide some feedback mechanism from Dom0 to DomU.
In our case it is technically impossible to provide precise period interrupt (mostly because our backend is a user space application). The best we can implement it is provide number of frames (time, bytes etc.) consumed by real HW. This info will be outdated due to different delays but we can provide precise timestamps when this info was acquired.
Would this info be useful to update the frontend driver state?
If you have in mind any other solution we would appreciate.
--
Best Regards,
Oleksandr Grytsov.