VM App - PCIDriverKit Entitlement for Thunderbolt

I want to help contribute a feature in a virtual-machine app in macOS that supports PCIe device passthrough over thunderbolt.

I have a question about the entitlements. Since I do not represent the GPU vendors, would I be allowed to get a driver signed that matches GPU vendor IDs? Is there such a thing as wildcard entitlement for PCIDriverKit?

I don't want end-users to have to disable SIP to be able to use this. Any suggestions/leads? Thank you.

I want to help contribute a feature in a virtual-machine app in macOS that supports PCIe device passthrough over Thunderbolt.

If you haven't already, please file a bug asking us to provide a solution for this and then post the bug number back here. This might be semi-solvable through DriverKit, but this is really something the system is in a better position to solve.

Is there such a thing as wildcard entitlement for PCIDriverKit?

Strictly speaking, yes, as that's how the development-only entitlement variant described here works. However, that's not an entitlement configuration I'd expect us to ever approve.

I have a question about the entitlements. Since I do not represent the GPU vendors, would I be allowed to get a driver signed that matches GPU vendor IDs?

That's ultimately up to the approval team, but I believe there have been cases where the entitlement has been granted to developers that don't directly "own" a particular vid/pid.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

VM App - PCIDriverKit Entitlement for Thunderbolt
 
 
Q