Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Allow resource names for additional resource types #16

Open
zdobersek opened this issue Feb 27, 2024 · 0 comments
Open

[FR] Allow resource names for additional resource types #16

zdobersek opened this issue Feb 27, 2024 · 0 comments

Comments

@zdobersek
Copy link

RMV userdata tokens can specify debugging-purpose names for specific resources, making for a better experience when examining resources through GUI. These tokens can be generated through object-naming entrypoints in the VK_EXT_debug_marker and VK_EXT_debug_utils extensions, but they could also be used to associate internal resources with some descriptive name.

The problem at the moment is in the RMV application the name-carrying userdata tokens are only applied to resources of three types: buffers, images and heaps. This filter is applied here:
https://github.com/GPUOpen-Tools/radeon_memory_visualizer/blob/master/source/backend/rmt_resource_userdata.cpp#L330

The naming functionality is great, but it would be perfect it could be applied to resources of any type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant