This section applies only to Windows 7 and later, and Windows Server 2008 R2 and later versions of Windows operating system.
The runtime can map a dynamic resource (through a call to the driver's ResourceMap function) on a deferred context, as the Direct3D version 11 API ensures that the first use of the mapped dynamic resource is to discard the previous contents. The best option is to create a new dynamic resource on each discard over continually using the original dynamic resource. The creation of this aliased resource is required to allow operations that are done to the virtual dynamic resource in the timeline of the deferred context to not affect the operations that are done to the virtual dynamic resource in the timeline of the immediate context. Remember, that deferred contexts are merely recording operations that eventually are actualized during a call to the driver's CommandListExecute function. When a dynamic resource is used, the original intentions of the application are preserved, and write-combined GPU-accessible memory is provided to the application (that is, the memory is optimized for single-use CPU upload).
Each resource map can provide the pointers directly to the aliased resource. There is an additional burden on deferred context recording to implement this type of aliasing. For example, deferred context recording might require new views to be created for aliased textures. Integrations with driver aliasing are necessary and seem plausible to do. When a command list is executed, the last context-local created resource (to satisfy the map-discard calls) must be substituted as the "current" resource that backs the dynamic resource for the immediate context, and so on.
A call to the driver's ResourceCopy function to copy a resource to a dynamic resource must still be supported both on the deferred context, after map-discard calls, and on the immediate context after a call to the driver's CommandListExecute function, where the local deferred context resource is ideally swapped into the immediate context version of the "current" resource. A call to the driver's ResourceCopy function with dynamic-resource destinations is not frequently used, so you should use a copy-on-write mechanism. If ResourceCopy is called that would affect either the dynamic resource on the deferred context after a map-discard call or on the immediate context that holds a command list local resource as current, a new resource should be conceptually allocated to provide the new destination of the copy, and the old resource must be copied to the new resource (if the operation is a ResourceCopyRegion).