ZC v1095 : Performance optimization in UMD w.r.t texture 2d

Author: sraman4

DVServerKMD/DVServerKMD.vcxproj

@@ -110,6 +110,9 @@ Signtool sign /v /fd sha256 /s PrivateCertStore /n DVServerKMD /tr http://timest
 Signtool sign /v /fd sha256 /s PrivateCertStore /n DVServerKMD /tr http://timestamp.digicert.com /td sha256 $(OutDir)DVServerKMD\DVServerKMD.sys
 certmgr -del -c -n "DVServerKMD" -s PrivateCertStore</Command>
     </PostBuildEvent>
+    <DriverSign>
+      <FileDigestAlgorithm>sha1</FileDigestAlgorithm>
+    </DriverSign>
   </ItemDefinitionGroup>
   <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
     <ClCompile>
@@ -132,6 +135,9 @@ Signtool sign /v /fd sha256 /s PrivateCertStore /n DVServerKMD /tr http://timest
 Signtool sign /v /fd sha256 /s PrivateCertStore /n DVServerKMD /tr http://timestamp.digicert.com /td sha256 $(OutDir)DVServerKMD\DVServerKMD.sys
 certmgr -del -c -n "DVServerKMD" -s PrivateCertStore</Command>
     </PostBuildEvent>
+    <DriverSign>
+      <FileDigestAlgorithm>sha1</FileDigestAlgorithm>
+    </DriverSign>
   </ItemDefinitionGroup>
   <ItemGroup>
     <FilesToPackage Include="$(TargetPath)" />

DVServerUMD/DVServer/DVServer.vcxproj

@@ -265,6 +265,9 @@ Signtool sign /v /fd sha256 /s PrivateCertStore /n DVServer /tr http://timestamp
 Signtool sign /v /fd sha256 /s PrivateCertStore /n DVServer /tr http://timestamp.digicert.com /td sha256 $(OutDir)DVServer\DVServer.dll
 certmgr -del -c -n "DVServer" -s PrivateCertStore</Command>
     </PostBuildEvent>
+    <DriverSign>
+      <FileDigestAlgorithm>sha1</FileDigestAlgorithm>
+    </DriverSign>
   </ItemDefinitionGroup>
   <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
     <ClCompile>
@@ -293,6 +296,9 @@ Signtool sign /v /fd sha256 /s PrivateCertStore /n DVServer /tr http://timestamp
 Signtool sign /v /fd sha256 /s PrivateCertStore /n DVServer /tr http://timestamp.digicert.com /td sha256 $(OutDir)DVServer\DVServer.dll
 certmgr -del -c -n "DVServer" -s PrivateCertStore</Command>
     </PostBuildEvent>
+    <DriverSign>
+      <FileDigestAlgorithm>sha1</FileDigestAlgorithm>
+    </DriverSign>
   </ItemDefinitionGroup>
   <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|ARM'">
     <ClCompile>

DVServerUMD/DVServer/Driver.cpp

@@ -588,6 +588,11 @@ void SwapChainProcessor::cleanup_resources()
 		CloseHandle(m_GPUResourceMutex);
 	}
 
+	if ((m_destimage != NULL) && (m_Device != NULL)) {
+		m_Device->DeviceContext->Unmap(m_destimage, 0);
+		m_destimage->Release();
+	}
+
 #ifdef DVSERVER_HWDCURSOR
 	// ****** Cursor Resources ******
 	if (devHandle_cursor != INVALID_HANDLE_VALUE)
@@ -874,13 +879,13 @@ int SwapChainProcessor::GetFrameData(std::shared_ptr<Direct3DDevice> dvserver_de
 			ERR("Failed Staging Buffer invalid configurations\n");
 			return DVSERVERUMD_FAILURE;
 		}
-	}
 
-	/* Create Texture2D with the staging descriptor parameters */
-	dvserver_device->Device->CreateTexture2D(&m_staging_desc, NULL, &m_destimage);
-	if (m_destimage == NULL) {
-		ERR("Failed Staging Buffer CreateTexture2D is NULL\n");
-		return DVSERVERUMD_FAILURE;
+		/* Create Texture2D with the staging descriptor parameters */
+		dvserver_device->Device->CreateTexture2D(&m_staging_desc, NULL, &m_destimage);
+		if (m_destimage == NULL) {
+			ERR("Failed Staging Buffer CreateTexture2D is NULL\n");
+			return DVSERVERUMD_FAILURE;
+		}
 	}
 
 	WaitForSingleObject(m_GPUResourceMutex, INFINITE);
@@ -948,8 +953,6 @@ int SwapChainProcessor::GetFrameData(std::shared_ptr<Direct3DDevice> dvserver_de
 		return DVSERVERUMD_FAILURE;
 	}
 
-	dvserver_device->DeviceContext->Unmap(m_destimage, 0);
-	m_destimage->Release();
 	return DVSERVERUMD_SUCCESS;
 }
 

Readme.txt

@@ -57,31 +57,6 @@ use the below command to get the display port name for that particular board
 	3.1) In services.msc, we need to check if QEMU Guest Agent in running state
 	3.2) Open Device Manager --> under system devices --> VirtIO Serial Driver should showup
 
------------------------------------------------------------
-#####  DVServer Unit Level Testing (ULT) Application  #####
------------------------------------------------------------
-- DVServerULT will imitate DVServerUMD which will talk to DVServerKMD through realtime IOCTL & run below tests.
-- Basically, it will help to isolate any complex issues on the DVServerKMD
-- ULT is an user mode application, this will test the VirtIO GPU pipeline. The ULT will directly interact with KMD via IoCTL's and send the solid color image frame address. 
-- Apart from this, it can get the supported QEMU EDID and displays all the supported modes
-
-IMPORTANT NOTE : This is a parallel UMD component (like DVServerUMD), so we should never attempt to run this ULT when the DVServerUMD is streaming the display frame buffer address
-
-Steps to avoid DVServerUMD:
-1. Install ZC with above method
-2. Go to Device manager -->Display Adapter -->DVServerUMD Device & disable
-3. Screen freeze will be expected & try to reboot the VM from QEMU windows
-4. After reboot, ZC will be disabled
-5. Now we can run DVServerULT.exe as mentioned below.
-
-How to Use:
-[CMD] .\DVServerULT.exe <testcase name>
-Entering the tescase number as a command line arguement is optional. If no arguement is provided, the list of test cases will be displayed.
-edidinfo --> Will display the QEMU supported resolutions and EDID info
-solidframe --> this will perform "Static Frame Test". From list of resolutions, select the resolution for which the static color frame is to be generated and displayed on QEMU
-multicolor --> this will perform "Multicolor Frames Test". From list of resolutions, select the resolution for which the multi color frame to be generated and displayed on QEMU
-multipattern --> this will perform "Multicolor Multiresolution Frames Test". For all the resolutions, multicolor frames are to be generated displayed in a continuous loop on QEMU
-
 -----------------------------------------------------------
 #####  Steps to capture and decode the ETL trace  #####
 -----------------------------------------------------------