<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body> Hello, we are developing a custom hypervisor backend for GVT which (from the mediators perspective) behaves like XEN. Currently, we are working with the Linux Kernel v5.4.41 and we are trying to pass a custom EDID to a given vGPU. The code flow roughly looks like this: <code>vgpu = intel_gvt_ops->vgpu_create();</code> <code>port = intel_vgpu_port(vgpu, port);</code><code> </code> <code>edid_data = intel_vgpu_edid_block(port);</code> <code>memcpy(edid_data, custom_edid, EDID_SIZE);</code> We are wondering how the <code>set_edid</code> callback of the <code>intel_gvt_mpt</code> is meant to be used to receive the correct port where the virtual display is attached. In v5.4.41 it seems, the default port is PORT_B and the mediator only calls <code>set_edid</code> on certain platforms where it is a different port. Is this correct? Is there any other method to receive the correct port? It seems that in v5.4.41 the mediator misses to call <code>set_edid</code> if the platform <code>IS_COFFEELAKE</code>, which leads to a crash because we then assume the default PORT_B where no memory is allocated for the EDID data. Also in some later commits [1] the behavior is changed and the <code>set_edid</code> callback is always called passing PORT_D. Does that mean that the virtual display is always attached at PORT_D on newer versions of GVT? Greetings, Stefan [1] <a class="moz-txt-link-freetext" href="https://github.com/torvalds/linux/commit/0178f4ce3c3be4d9784c88ed512816eb653a717b">https://github.com/torvalds/linux/commit/0178f4ce3c3be4d9784c88ed512816eb653a717b</a> </body> </html>