You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
QAT plugin needs custom apparmor rules since it fails (on certain distros) on the attempt to write to VFIO/UIO new_id. setupDeviceIDs() is somewhat legacy since the preferred approach is driver_override.
Describe the solution you'd like
the new_id mechanism was added way before we had the initcontainer support in place. furthermore, at least for vfio-pci we don't need it at all if the driver uses ids=8086:<qat VF dev IDs>.
the suggestion is to drop write attemps to new_id and move the corresponding functionality to qat-init.sh. With this, we can drop apparmor policies from the plugin.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
QAT plugin needs custom apparmor rules since it fails (on certain distros) on the attempt to write to VFIO/UIO
new_id
.setupDeviceIDs()
is somewhat legacy since the preferred approach isdriver_override
.Describe the solution you'd like
the
new_id
mechanism was added way before we had the initcontainer support in place. furthermore, at least for vfio-pci we don't need it at all if the driver usesids=8086:<qat VF dev IDs>
.the suggestion is to drop write attemps to
new_id
and move the corresponding functionality toqat-init.sh
. With this, we can drop apparmor policies from the plugin.Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: