-
Notifications
You must be signed in to change notification settings - Fork 117
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
Add used resolutions info #1167
base: dev
Are you sure you want to change the base?
Add used resolutions info #1167
Conversation
gfxrecon-info reports resolutions used in vulkan traces based on data provided in vkCreateSwapchainKHR and vkCreateSharedSwapchainsKHR calls. Change-Id: I91118d1c7749662765d45e180c61937dd0297816
Author bartosz-muszarski-arm not on autobuild list. Waiting for curator authorization before starting CI build. |
Could this be accomplished by a script parsing the output of |
CI gfxreconstruct build queued with queue ID 2227. |
CI gfxreconstruct build # 2896 running. |
As an example, here's a
|
CI gfxreconstruct build # 2896 passed. |
Yes, the same data can be generated from a json-converted trace. I would argue this is still more convenient to use on a daily basis. We use the resolution information along with application name and total frame count which we get from gfxrecon-info already. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me except if there are no swapchains created (e.g. vulkaninfo
) then the output is Used resolutions
and then nothing else. I think there should be no output if resolution.size() == 0
.
Okay, sounds good to me. I added a note about empty |
Change-Id: If09c70784503e4344bab2a3294245505027874ab
CI gfxreconstruct build queued with queue ID 6518. |
CI gfxreconstruct build # 2983 running. |
CI gfxreconstruct build # 2983 failed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had the one thought about vulkan.hpp.
Also your branch is failing in our internal CI because it's missing commit 32496a2 committed to dev
on June 29. If you rebase on current dev
I think it will probably pass our internal CI. Sorry, I think these are the last two items; thanks for being patient and sticking with us!
@@ -30,11 +30,14 @@ | |||
#include "generated/generated_vulkan_struct_decoders.h" | |||
#include "generated/generated_vulkan_consumer.h" | |||
#include "util/defines.h" | |||
#include "vulkan/vulkan.hpp" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I didn't catch this on first pass. This would be the first inclusion of VulkanHpp and I want to be a little more deliberate about adding it. Can you just use VkExtent2D?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bartosz-muszarski-arm if you haven't done this already I see how it smooths out the feature you added and I'm not in principle against it. I'm doing a straw poll to see if anyone has any issues with including VulkanHpp.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we at least reduce this to just including the structs header and not taking in the entire C++ wrapper?
#include <vulkan/vulkan_structs.hpp>
EDIT: vulkan_hash.hpp
included on the next line includes vulkan.hpp
anyway...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And also turn off every feature we don't need in the headers that has a macro that defaults to enabled. e.g. in our CMake configs for all projects define VULKAN_HPP_NO_STRUCT_SETTERS
. We can then turn stuff on when we need it, where we need it.
@@ -57,6 +60,7 @@ class VulkanStatsConsumer : public gfxrecon::decode::VulkanConsumer, public gfxr | |||
uint64_t GetMaxAllocationSize() const { return max_allocation_size_; } | |||
uint64_t GetAnnotationCount() const { return annotation_count_; } | |||
const std::vector<std::string>& GetOperationAnnotationDatas() const { return operation_annotation_datas_; } | |||
const auto& GetResolutions() const { return resolutions_; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a fan of auto
here where it forces the future contributors to scroll down the file to know what the function they might want to call actually returns (std::unordered_set<vk::Extent2D>
).
CI gfxreconstruct build queued with queue ID 10777. |
CI gfxreconstruct build # 3020 running. |
CI gfxreconstruct build # 3020 failed. |
gfxrecon-info reports resolutions used in vulkan traces based on data provided in vkCreateSwapchainKHR and vkCreateSharedSwapchainsKHR calls.
Sample output: