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

Current driver model - WDDM | TCC #43

Open
JeremyMain opened this issue May 22, 2017 · 5 comments
Open

Current driver model - WDDM | TCC #43

JeremyMain opened this issue May 22, 2017 · 5 comments

Comments

@JeremyMain
Copy link
Owner

@JeremyMain JeremyMain commented May 22, 2017

Fred's request:
report and store in the GPD file the current (at profile time) the driver model / version:
WDDM version or TCC

@JeremyMain
Copy link
Owner Author

@JeremyMain JeremyMain commented Jun 8, 2017

in NVML, nvmlDeviceGetDriverModel ( ) will return the driver model in use for each GPU

  • to add this to the GPU information and serialization.
@JeremyMain
Copy link
Owner Author

@JeremyMain JeremyMain commented Aug 3, 2017

Added to the GPU name
image

However, since I do not handle multi-GPU information in the UI it will be of little value.
I am still reworking the UI to better handle multiple GPU information display but not targeting the next 1.05 release.

I will leave this open until it is possible to see the TCC / WDDM mode of all the GPUs.

@JeremyMain
Copy link
Owner Author

@JeremyMain JeremyMain commented Aug 25, 2017

To add all of the detected GPUs I will need to dynamically expand the "System Information" group.

@JeremyMain
Copy link
Owner Author

@JeremyMain JeremyMain commented Feb 16, 2019

Multi-GPU information is not displayed in the "System Information" panel.
That will be added in a future version.

@JeremyMain
Copy link
Owner Author

@JeremyMain JeremyMain commented Nov 26, 2019

Multi-GPU support and information about if the driver is WDDM or TCC mode has been added in v1.07b

@JeremyMain JeremyMain added this to the v1.07b milestone Nov 26, 2019
@JeremyMain JeremyMain self-assigned this Nov 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant