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 Williamson
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 th
Cool, that did the trick! Thank you Jordan!
20.05.2019, 23:35, "Jordan Glover" :
> On Sunday, May 19, 2019 6:45 PM, Alex Ivanov wrote:
>
>> Hello.
>> What is the proper way to do that? I have a unit that creates gvt device in
>> the system
>>
>> ExecStart = "sh -c 'echo a297db4a-f4c2-11e6-90f
Could Intel fix that?
Пересылаемое сообщение
20.05.2019, 15:18, "Andrei Borzenkov" :
On Mon, May 20, 2019 at 10:08 AM Mantas Mikulėnas wrote:
> On Sun, May 19, 2019 at 9:50 PM Alex Ivanov wrote:
>> Hello.
>> What is the proper way to do that? I have a unit that creates gvt
20.05.2019, 10:08, "Mantas Mikulėnas" :On Sun, May 19, 2019 at 9:50 PM Alex Ivanov wrote:Ideally I would to like to start this service when :00:02.0 device appears in the system, but the problem is that /sys/bus/pci/devices/:00:02.0/mdev_supported_types/ tree is populated