IMPORTANT: migrate to oneVPL for newer Intel GPUs support

[dmitryermilov]

Intel® Media SDK lifetime comes to an end in a form it exists right now. In particular,

• API 1.35 is projected to be the last API of 1.x API series
• Runtime library (libmfxhw64.so.1) is not planned to get support of new Gen platforms (ADL-S, ADL-P, and above)
• Project is going to be supported in maintenance mode, critical fixes only

All future development is planned to happen within oneVPL library and its runtime implementations which are direct successors of Intel® Media SDK. oneVPL introduces API 2.x series which is not backward compatible with API 1.x series (some features got dropped). New VPL Runtime for Gen Graphics (libmfx-gen.so.1.2) comes with the support of new Gen platforms.

What should be packaged?

Attn. @dbermond, @jbeich, @sebastinas, @sndirsch, @tjaalton

Media SDK and oneVPL support Intel GPUs starting from gen8 BDW. However:

• New VPL Runtime for Gen Graphics (libmfx-gen.so.1.2) supports platforms starting from Gen12 - TGL, DG1, RKL, ADL-S, ADL-P
• Media SDK runtime (libmfxhw64.so.1) supports "legacy" platforms up to (some!) Gen12 platforms - BDW, SKL, KBL, CFL, ... , TGL, DG1

MSDK and oneVPL dispatcher libraries (libmfx.so.1 or libvpl.so.2) load one of the above runtimes depending on the underlying GPU platform.

Thus, the following repos needs to be packaged to cover full range of MSDK/VPL supported platforms:

• https://github.com/oneapi-src/oneVPL (>=v2021.6.0)
• https://github.com/Intel-Media-SDK/MediaSDK (>=intel-mediasdk-21.3.4)
• https://github.com/oneapi-src/oneVPL-intel-gpu (>=intel-onevpl-21.3.4)

Status of dependent projects

Project	Status
ffmpeg	Not yet switched to oneVPL, patches pending package adoption by Linux distros
gst-plugins-bad	oneVPL support enabled

[dbermond]

Thank you for the information. Very appreciated!

oneVPL packages on Arch Linux:

• https://aur.archlinux.org/packages/onevpl/
• https://aur.archlinux.org/packages/onevpl-cpu/
• https://aur.archlinux.org/packages/onevpl-intel-gpu/

I have placed them on the AUR (Arch User Repository) for the time being. Planning to move them to the official repositories later, as there is still low user usage and no dependent applications using them yet.

Packaging suggestions are welcome :)

[sebastinas]

I don't intend to work on packaging oneVPL for Debian.

[sndirsch]

Hello Dmitry

Thanks a lot for all this information! Very much appreciated. :-) I almost finished packaging for (open)SUSE, but then I unfortunately noticed (well, our legal team did) that oneVPL-intel-gpu comes with various source files with proprietary Intel license.

oneVPL-intel-gpu-intel-onevpl-21.3.4/api/mediasdk_structures/ts_struct_decl.h oneVPL-intel-gpu-intel-onevpl-21.3.4/builder/FindGTest.cmake oneVPL-intel-gpu-intel-onevpl-21.3.4/builder/FindGlobals.processed.cmake oneVPL-intel-gpu-intel-onevpl-21.3.4/builder/FindVTune.cmake oneVPL-intel-gpu-intel-onevpl-21.3.4/contrib/ipp/src/ippversion.h

Is this an oversight or intentional? Can this be checked? (open)SUSE would be interested in shipping this library, but is blocked for now. :-( I also opened an issue for that.

https://github.com/oneapi-src/oneVPL-intel-gpu/issues/183

Thanks, Stefan

On Tue, 28 Sept 2021 at 22:11, Dmitry Ermilov @.***> wrote:

Intel® Media SDK lifetime comes to an end in a form it exists right now. In particular,

• API 1.35 is projected to be the last API of 1.x API series
• Runtime library (libmfxhw64.so.1) is not planned to get support of new Gen platforms (ADL-S, ADL-P, and above)
• Project is going to be supported in maintenance mode, critical fixes only

All future development is planned to happen within oneVPL https://github.com/oneapi-src/oneVPL library and its runtime implementations which are direct successors of Intel® Media SDK. oneVPL introduces API 2.x series which is not backward compatible with API 1.x series (some features got dropped https://spec.oneapi.com/versions/latest/elements/oneVPL/source/appendix/VPL_intel_media_sdk.html). New VPL Runtime for Gen Graphics https://github.com/oneapi-src/oneVPL-intel-gpu (libmfx-gen.so.1.2) comes with the support of new Gen platforms. What should be packaged?

Attn. @dbermond https://github.com/dbermond, @jbeich https://github.com/jbeich, @sebastinas https://github.com/sebastinas, @sndirsch https://github.com/sndirsch, @tjaalton https://github.com/tjaalton

Media SDK and oneVPL support Intel GPUs starting from gen8 BDW. However:

• New VPL Runtime for Gen Graphics https://github.com/oneapi-src/oneVPL-intel-gpu%3E (libmfx-gen.so.1.2) supports platforms starting from Gen12 - TGL, DG1, RKL, ADL-S, ADL-P
• Media SDK runtime (libmfxhw64.so.1) supports "legacy" platforms up to (some!) Gen12 platforms - BDW, SKL, KBL, CFL, ... , TGL, DG1

MSDK and oneVPL dispatcher libraries (libmfx.so.1 or libvpl.so.2) load one of the above runtimes depending on the underlying GPU platform.

Thus, the following repos needs to be packaged to cover full range of MSDK/VPL supported platforms:

• https://github.com/oneapi-src/oneVPL (>=v2021.6.0)
• https://github.com/Intel-Media-SDK/MediaSDK (>=intel-mediasdk-21.3.4)
• https://github.com/oneapi-src/oneVPL-intel-gpu (>=intel-onevpl-21.3.4)

Status of dependent projects Project Status ffmpeg Not yet switched to oneVPL, patches pending package adoption by Linux distros gst-plugins-bad oneVPL support enabled

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Intel-Media-SDK/MediaSDK/issues/2799, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7BK3JH62OAQ37AYTTRPKTUEIOQLANCNFSM5E6HNR5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[dvrogozh]

oneVPL-intel-gpu comes with various source files with proprietary Intel license

That's an oversight. We fixed it in this commit: https://github.com/oneapi-src/oneVPL-intel-gpu/commit/ccfd3c8a4238dd1fc05f66f47f5a967df1255018

Please, let us know if you will spot anything else.

[sndirsch]

Thanks a lot! Looks good! Everything addressed from our side! :

Stefan

On Tue, 12 Oct 2021 at 03:59, Dmitry Rogozhkin @.***> wrote:

oneVPL-intel-gpu comes with various source files with proprietary Intel license

That's an oversight. We fixed it in this commit: @.***

Please, let us know if you will spot anything else.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[sndirsch]

Hello again. Unfortunately I found a similar issue. This time in oneapi-src/oneVPL sources. It seems the component contains code licensed under "MS Vistual Studio" licsense. AFAIK this is incompatible to GPL-3.0 license.i.e. you can't link GPL 3.0 sources against libvpl. This makes it difficult for a Linux distributor to ship this library. :-( Is this an oversight, intentional or just can't be changed? I've opened an issue for this, but haven't seen any response to this up to now. :-(

https://github.com/oneapi-src/oneVPL/issues/27

Thanks, Stefan

On Tue, 12 Oct 2021 at 10:36, Stefan Dirsch @.***> wrote:

Thanks a lot! Looks good! Everything addressed from our side! :

Stefan

On Tue, 12 Oct 2021 at 03:59, Dmitry Rogozhkin @.***> wrote:

oneVPL-intel-gpu comes with various source files with proprietary Intel license

That's an oversight. We fixed it in this commit: @.***

Please, let us know if you will spot anything else.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Intel-Media-SDK/MediaSDK/issues/2799#issuecomment-940790973, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7BK3OHGUJKVDHIE35JLSDUGPXQZANCNFSM5E6HNR5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[eero-t]

Summarizing here....

Unfortunately I found a similar issue. This time in oneapi-src/oneVPL sources. It seems the component contains code licensed under "MS Vistual Studio" license. AFAIK this is incompatible to GPL-3.0 license.i.e. you can't link GPL 3.0 sources against libvpl. This makes it difficult for a Linux distributor to ship this library. :-( Is this an oversight, intentional or just can't be changed?

According to https://github.com/oneapi-src/oneVPL/issues/27 this was just a misunderstanding (that license applies only to Windows builds which are not distributed under GPL) which is / will be cleared in the documentation.

Additionally, "oneVPL-intel-gpu" (Intel GPU backend for oneVPL frontend) project build issue with GCC v11.2 (used in Ubuntu 21.10 and 22.04) is now fixed, but there is not yet a tagged version with that fix.

[dvrogozh]

project build issue with GCC v11.2 is now fixed, but there is not yet a tagged version with that fix

Yes, fixed in https://github.com/oneapi-src/oneVPL-intel-gpu/commit/a8702a9eb94a306ec8f592b5fcac41c84564f7c4. Will go into one of the next release or release updates.