D3D Cross Proc Sharing

This automated test verifies support for the cross-process resource sharing in Microsoft® Direct3D® version 9.

This topic applies to the following test jobs:

  • D3D Cross Proc Sharing

  • D3D Cross Proc Sharing (WoW64)

Test details

Associated requirements

Device.Graphics.AdapterRender.MinimumDirectXLevel

See the device hardware requirements.

Platforms

Windows 7 (x64) Windows 7 (x86) Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows Server 2012 (x64) Windows Server 2008 R2 (x64) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86 Windows Server 2012 R2

Expected run time

~8 minutes

Categories

Certification Functional

Type

Automated

 

Running the test

Before you run the test, complete the test setup as described in the test requirements: Graphic Adapter or Chipset Testing Prerequisites.

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Graphics Testing.

More information

This test includes the following test cases:

  • CONF:Create. Create a shared resource.

  • CONF:Open. Create and open a shared resource in the same process.

  • CONF:ClientOpen. Create a shared resource in Process 1, and open that resource in Process 2.

  • CONF:Verify. Process 2 verifies that the content of the opened resource is correct.

  • CONF:Fill. Process 2 fills the open resource, and Process 1 verifies the content.

  • CONF:Lock. This test case initiates the following actions:

    • Process 1 locks the resource,

    • Process 2 attempts to lock the resource (this attempt should fail)

    • Process 2 attempts to unlock the resource (this attempt should fail)

    • Process 1 unlocks the resource

    • Process 2 attempts to lock the resource (this attempt should fail)

    • Process 2 attempts to unlock the resource (this attempt should fail)

    • Process 1 attempts to unlock the resource again (this attempt should fail)

  • CONF:ReleaseSourceUseOpen. This test case completes the following actions:

    • Process 1 creates a resource

    • Process 2 opens the resource and verifies the content of the resource

    • Process 1 releases the resource

    • Process 2 uses the resource

    • Process 1 opens the resource and then updates the resource content.

You can test multiple resource types, or just one by using the command line. To run with only one resource type, use -ResourceType:<ResourceType>.

You can use the following resource types:

  • OFFSCREENPLAIN

  • DEPTHSTENCIL

  • RENDERTARGET

  • TEXTURE

  • VOLUMETEXTURE

  • VOLUMETEXTURE

  • INDEXBUFFER

Command syntax

Command option Description

D3DCrossProcShare -CrossProcShare_Conf -M:1 -whql -logclean

This command runs the D3D Cross Proc Sharing test job.

D3DCrossProcShare -CrossProcShare_Conf -M:1 -whql -logclean

This command runs the D3D Cross Proc Sharing (WoW64) test job.

 

Note  

For command line help for this test binary, type /?.

 

File list

File Location

Configdisplay.exe

<[testbinroot]>\nttest\windowstest\tools

D3d10ref.dll

<[testbinroot]>\nttest\graphics\d3d\support\

D3d11ref.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dcompiler_test.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3DCrossProcShare.exe

<[testbinroot]>\nttest\windowstest\graphics\d3d\conf\

D3dref.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support

D3dref8.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dref9.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx10_test.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx11_TEST.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx8d.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx9_TEST.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

Fpstate.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\utility\

Modechange.exe

<[testbinroot]>\nttest\windowstest\graphics\d3d\utility\

TDRWatch.exe

<[testbinroot]>\nttest\windowstest\graphics\

Vbswap.x

<[testbinroot]>\nttest\windowstest\graphics\d3d\conf\

 

 

 

Send comments about this topic to Microsoft