KhronosGroup / KhronosGroup/Vulkan-Tools

vulkaninfo cannot get info on GPU 1 only

Open
#840 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement vulkaninfo
Dominant language
C++
Stars
493
Forks
202
Avg merge
1h 37m
Merged PRs (30d)
4

Description

Hi,

Unless I completely misunderstand how to use the vulkaninfo tool on the command line, there's something strange afoot here..
If I run the tool without any arguments, I get a list like this:

Layers: count = 4
=================
VK_LAYER_INTEL_nullhw (INTEL NULL HW) Vulkan version 1.1.73, layer version 1:
	Layer Extensions: count = 0
	Devices: count = 3
		GPU id = 0 (AMD Radeon Graphics (RADV REMBRANDT))
		Layer-Device Extensions: count = 0

		GPU id = 1 (NVIDIA GeForce RTX 3070 Ti Laptop GPU)
		Layer-Device Extensions: count = 0

		GPU id = 2 (llvmpipe (LLVM 15.0.7, 256 bits))
		Layer-Device Extensions: count = 0

[...]

According to the help message (vulkaninfo --help) I should be able to get info on a select GPU:

[-j=<gpu-number>, --json=<gpu-number>]
                    For a multi-gpu system, a single gpu can be targetted by
                    specifying the gpu-number associated with the gpu of 
                    interest. This number can be determined by running
                    vulkaninfo without any options specified.

And then I try to run it like this:

vulkaninfo -j=1

-- but I only get the help message, alluring the fact that I'm possibly using the tool in the wrong way. And I do not want a JSON output, but rather text, which is more easily readable.

Platform is Ubuntu 23.04.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported commands, vulkaninfo and vulkaninfo -j=1, and compare their output with vulkaninfo --help. Trace the command-line handling for GPU selection and text versus JSON output. Done means a user can target GPU 1 as documented and obtain readable text, or the help clearly documents the supported syntax and output mode.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.