- Add GMM lib DLL project in Cmake file.
- All code changes needed to make GMM lib DLL are under GMM_LIB_DLL macro.
- Add ProcessSingleton elements in DLL context.
- Establish a link between DLL singleton Data and Process Singleton data in ProcessContext in KMD for ProcessSingleton elements. This is needed when GMM lib exists in both static and DLL mode.
- Overloaded Create and Destroy GMM objects member fucntions of ClientContext to take memory Allocators and Deallocators from Clients. This is needed for Clients like VK.
Change-Id: Iab4e596723a0fa0eede262bdb26436ba8a7d5cc1
- These changes are for enabling unified GMM lib target. Unified GMM lib target will not have any clients specific build macros.
- Addition of GMM Old API Translation Layer for backward compatibilty for all GMM APIs across ALL UMD clients.
- Creation of Global Client Context handle only for backward compatible clients. This shall be replaced by client handle by clients moving to new API.
- Add new definitions for GMM Device Callbacks structure.
- Add new definitions for KMDaf related macros only for GMM to be used bu unified GMM lib.
- Makes ClientContext class member of Resinfo class
- GmmLib cmake change to add new igfxgmmumd unified static lib project
Change-Id: I913192e0879e565fb369c364fcba573a18b3fe13
This issue happens only on specific panel (LG ULTRAFINE 5K DISPLAY) on CNL
GMM doesn't need to enforce display restrictions since all allocated resources aren't always displayed on Intel hardware or through one pipe.
Change-Id: I2804f04ba63fcbe88582f827b16c21b7840d5b71
- Makes ClientContext class member of Resinfo and PageTableMgr class
- Addition of OCL Translation Layer
- GmmLib cmake change to add new igfxgmmumd unified static lib project
Change-Id: If155bafad29086ab5309c24f1f8a1862f92eb654
vipuldas