https://bugs.winehq.org/show_bug.cgi?id=35205
--- Comment #23 from Henri Verbeet hverbeet@gmail.com --- Yes. Unfortunately I'm not entirely sure about the best way forward at this point, which is most of the reason for nothing happening right now. It may be best to attach the patches to this bug for the time being, to prevent them getting lost.
For what it's worth, the main issue is that it isn't clear how dirty areas should interact with the resource location management. To some extent that's mostly a matter of picking something and applying it consistently, but there are a fair number of interactions with other code and cases to go through. E.g., should wined3d_texture_load_location() resolve dirty areas or not?
Aside from those, there's e.g. the issue that dirty areas are accessed from both the wined3d command stream thread and the application thread (e.g., wined3d_cs_exec_add_dirty_texture_region() and wined3d_device_update_texture()), although that's a comparatively minor issue.