> On May 9, 2023, at 12:16, Timo Rothenpieler <t...@rothenpieler.org> wrote:
>
> On 09/05/2023 12:11, rcombs wrote:
>> - cuDeviceGetUuid_v2, giving distinct IDs for different MIG instances
>> - cuDeviceGetLuid, giving a Win32 LUID to match with DXGI and other APIs
>> - cuDeviceGetByPCIBusId, retrieving a device that matches a PCI bus ID string
>> - cuDeviceGetPCIBusId, giving a PCI bus ID string for a device
>
> Looks good to me. What do you need those for?
> Interop with D3D1x/Vulkan?
I'm fetching device lists with DXGI (windows) or libdrm (linux); these
functions seem to be the best way to correlate devices with those APIs.
Probably also useful for D3D/Vk interop, though; particularly the v2 UUID
function, as my guess is that the Vk interop code is probably broken in MIG
mode right now.
Would appreciate seeing this backported to the 11.x branches; it applies
cleanly.
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
