On Mon, 27 May 2019 08:20:08 +0300
gnido...@ya.ru wrote:
> Alex, thanks for the utlity!
> For now we just have used systemd.path helper [1] to wait for gvt device
> availability and fire up the service when its ready as was suggested by
> Jordan Glover.
>
> [1]
On Sun, May 26, 2019 at 09:28:36PM +0300, Alex Ivanov wrote:
> Could Intel fix that?
This is not tied only to the Intel driver. Like Alex said, mdev is not a
fundamental feature of the parent device. There was an attempt to fix this
behaviour in the mdev core driver last year [1], but was
Alex, thanks for the utlity!
For now we just have used systemd.path helper [1] to wait for gvt device
availability and fire up the service when its ready as was suggested by Jordan
Glover.
[1] https://www.freedesktop.org/software/systemd/man/systemd.path.html
26.05.2019, 22:54, "Alex
On Sun, 26 May 2019 21:28:36 +0300
Alex Ivanov wrote:
> Could Intel fix that?
I won't claim that mdev-core is bug free in this area, but it's
probably worth noting that mdev support isn't necessarily a fundamental
feature of the parent device, it could theoretically be enabled much
later than
