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

gfxrecon-info now prints vulkan physical device info #1992

Conversation

panos-lunarg
Copy link
Contributor

No description provided.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build queued with queue ID 356651.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 5933 running.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 5933 passed.

@@ -56,6 +58,26 @@ class VulkanStatsConsumer : public gfxrecon::decode::VulkanConsumer
uint64_t GetAllocationCount() const { return allocation_count_; }
uint64_t GetMinAllocationSize() const { return min_allocation_size_; }
uint64_t GetMaxAllocationSize() const { return max_allocation_size_; }
void GetPhysicalDeviceProperties(uint32_t& api_version,
Copy link
Contributor

@antonio-lunarg antonio-lunarg Jan 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: not a big fun of output parameters, I would introduce a new struct to group these.

@@ -377,6 +399,30 @@ class VulkanStatsConsumer : public gfxrecon::decode::VulkanConsumer
++dispatch_count_;
}

virtual void ProcessSetDevicePropertiesCommand(format::HandleId physical_device_id,
Copy link
Contributor

@bradgrantham-lunarg bradgrantham-lunarg Feb 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There will be one of these for every VkPhysicalDevice enumerated from an Instance so this needs to handle multiple SetDevicePropertiesCommand blocks. I have a .gfxr here with 2 of those blocks, one for an AMD discrete GPU and another for the integrated Intel GPU, so the blocks can't be assumed to have the same values.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be fixed now

@panos-lunarg panos-lunarg force-pushed the gfxrecon_info_print_physical_device_info branch from a88b7df to e7bca07 Compare February 3, 2025 13:04
@ci-tester-lunarg
Copy link

CI gfxreconstruct build queued with queue ID 363259.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6001 running.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6001 passed.

@panos-lunarg panos-lunarg force-pushed the gfxrecon_info_print_physical_device_info branch from e7bca07 to 13bfdc2 Compare February 4, 2025 06:17
@ci-tester-lunarg
Copy link

CI gfxreconstruct build queued with queue ID 364168.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6004 running.

@panos-lunarg panos-lunarg merged commit 0cbab3c into LunarG:dev Feb 4, 2025
9 checks passed
@panos-lunarg panos-lunarg deleted the gfxrecon_info_print_physical_device_info branch February 4, 2025 06:45
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

Successfully merging this pull request may close these issues.

5 participants