Windows 10: How to enable Windows 10 hardware accelerated GPU scheduling

WinLatest · Jul 7, 2020

If you follow Windows 10 development at all, you’ve probably heard this “Hardware accelerated GPU scheduling” buzzword that’s been going around since last year. At that point, Hardware-accelerated GPU scheduling was little more than just an option in Settings, but after driver update, the setting is now functional.

If you want to check out the new feature and see if it makes a difference to your apps or games, you would first need to check that you’re running Windows 10 version 2004 or Build 19041 in Settings > System > about.

On May 2020 Update, you would need to download Nvidia GeForce 451.48+ or Adrenalin 2020 Edition 20.5.1 Beta driver. While the Nvidia GeForce 451.48 enables GPU scheduling support for everyone, AMD has currently limited the availability of its new driver to beta testers.

Once you’ve got the latest version of Windows 10 and drivers, you can turn on or off the feature using Settings and Windows Registry.

Turn On or Off Hardware Accelerated GPU Scheduling in Settings

To enable hardware accelerated GPU scheduling on Windows 10, use these steps:

Open Start Menu and tap on Settings cog icon.

In Settings, click on ‘System’ and open ‘Display’ tab.

Under the “Multiple Displays” section, select “Graphics settings”.

Turn on or off “Hardware-accelerated GPU scheduling” option.

Restart the system.

Enable Hardware Accelerated GPU Scheduling using Registry

To force hardware accelerated GPU scheduling on Windows 10, use these steps:

Open Windows Search.

Search for ‘Registry’ and select the first option.

In Registry editor, navigate to ‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers’.

Locate DWORD tiled “HwSchMode” and use the following values:
1 = Off
2 = On

Restart the system.

Open Settings > Display > Graphics settings and toggle the option.

Understanding the hardware-accelerated GPU scheduling feature

Long story short, hardware accelerated GPU scheduling feature in Windows 10 represents a fundamental redesign in how Windows Display Driver Model (WDDM) works. While Microsoft says users won’t see any significant changes after activating it now, some believe that the feature could reduce input lag on low-end and mid-core processors.

Windows 10 hardware accelerated GPU scheduling feature passes most GPU scheduling tasks to a dedicated GPU-based scheduling processor, which should free up the CPU a little and can potentially equate to a small input lag improvement.

The post How to enable Windows 10 hardware accelerated GPU scheduling appeared first on Windows Latest

Weiterlesen...

Brink · Jul 7, 2020

Hardware Accelerated GPU Scheduling in Windows 10 version 2004

Abstract

You may have noticed a mysterious new optional feature called Hardware Accelerated GPU Scheduling appear in the advanced graphics settings page with the Windows 10 May 2020 update. The purpose of this blog is to give some background on this new feature and how we are introducing it. It is intended for folks curious about Windows internals. Remaining on the cutting edge of hardware innovation has always been a critical aspect of our graphics platform. Hardware Accelerated GPU Scheduling enables more efficient GPU scheduling between applications. For most users, this transition will be transparent. It is one of those things that if we do our job right, you will never know the transition happened. As the graphics platform continues to evolve, this modernization will enable new scenarios in the future.

WDDM GPU Scheduler

It has been almost 14 years since the introduction of the Windows Display Driver Model 1.0 (WDDM) and with it the introduction of GPU scheduling in Windows. Few likely remember the pre-WDDM days where applications could simply submit work to the GPU as much as they wanted. They submitted to a global queue where it was executed in a strict “first to submit, first to execute” fashion. These very rudimentary scheduling schemes were workable, at a time where most GPU applications were full screen games, being run one at a time.

With the transition to a broad set of applications using the GPU for richer graphics and animations, the platform needed to better prioritize GPU work to ensure a responsive user experience. Thus, the WDDM GPU scheduler was born.

Over time we have significantly enhanced the GPU scheduler at the heart of WDDM, supporting additional features and scenarios with each new WDDM version. However, throughout its evolution, one aspect of the scheduler was unchanged. We have always had a high-priority thread running on the CPU that coordinates, prioritizes, and schedules the work submitted by various applications.

This approach to scheduling the GPU has some fundamental limitations in terms of submission overhead, as well as latency for the work to reach the GPU. These overheads have been mostly masked by the way applications have traditionally been written. For example, an application would typically do GPU work on frame N, and have the CPU run ahead and work on preparing GPU commands for frame N+1. This buffering of GPU commands into batches allows an application to submit just a few times per frame, minimizing the cost of scheduling and ensuring good CPU-GPU execution parallelism.

An inherent side effect of buffering between CPU and GPU is that the user experiences increased latency. User input is picked up by the CPU during “frame N+1” but is not rendered by the GPU until the following frame. There is a fundamental tension between latency reduction and submission/scheduling overhead. Applications may submit more frequently, in smaller batches to reduce latency or they may submit larger batches of work to reduce submission and scheduling overhead.

Hardware-accelerated GPU scheduling

With Windows 10 May 2020 update, we are introducing a new GPU scheduler as a user opt-in, but off by default option. With the right hardware and drivers, Windows can now offload most of GPU scheduling to a dedicated GPU-based scheduling processor.

Windows continues to control prioritization and decide which applications have priority among contexts. We offload high frequency tasks to the GPU scheduling processor, handling quanta management and context switching of various GPU engines.

The new GPU scheduler is a significant and fundamental change to the driver model. Changing the scheduler is akin to rebuilding the foundation of a house while still living in it. To ensure a smooth transition we are introducing the new scheduler as an early-adopter, opt-in feature. During the transition we will gather large scale performance and reliability data as well as customer feedback.

We are adding UI to the Advanced Graphics Settings page to control enabling the new GPU scheduler. The settings page can be reached through Settings -> System -> Display -> Graphics Settings. If both your GPU and driver support the new GPU scheduler, the UI below will appear.

How to Turn On or Off Hardware Accelerated GPU Scheduling in Windows 10

Which GPUs will support Hardware Scheduling?

The new GPU scheduler will be supported on recent GPUs that have the necessary hardware, combined with a WDDMv2.7 driver that exposes this support to Windows. Please watch for announcements from our hardware vendor partners on specific GPU generations and driver versions this support will be enabled for.

Hardware accelerated GPU scheduling is a big change for drivers. While some GPUs have the necessary hardware, the associated driver exposing this support will only be released once it has gone through a significant amount of testing with our Insider population.

If you are an Insider and have chosen to install a build of Windows from our Fast or Slow distribution ring, you have been running a version of Windows with support for hardware accelerated GPU scheduling. You may have even been part of our experimentation!

As we get under-development drivers from our GPU manufacturer partners, we published these drivers to an Insider version of Windows Update (WU) where distribution is limited to the Insider population. In the Insider Fast Ring, we can run experiments where we silently toggle hardware accelerated GPU scheduling on, on behalf of some users such that we get a mix of users running with and without the new scheduler.

Through our experimentation platform and our telemetry system we can effectively run A/B experiments and compare how systems running with hardware accelerated GPU scheduling compare to systems running our old GPU scheduler. We monitor reliability telemetry such as kernel crashes (bluescreens), user mode crashes, GPU hangs, freeze/deadlocks as well as a limited set of performance metrics.

Once a driver completes support for hardware accelerated scheduling and accumulates enough execution time in our Insider Pool to demonstrate its reliability and performance, it is allowed to be promoted to the public version of Windows Update where it becomes available to everyone running the supported hardware.

Why not have hardware accelerated GPU scheduling on by default for all users given all the care taken before a driver can expose this support? Although we do a lot of validation through our Insider population, the number of system configurations and scenarios in the Insider population does not fully cover what can happen in our eco-system of more than a billion devices. Because hardware accelerated GPU scheduling is such a fundamental pillar of the graphics subsystem and used in absolutely everything that you do on your PC, we decided to introduce it initially as an opt-in to avoid any possible disruption. Users can opt-in through the UI and for new systems, OEM are encouraged to configure and validate their system with hardware accelerated GPU scheduling turned on from the factory.

What to expect when switching to the new GPU scheduler

The transition should be transparent, and users should not notice any significant changes. Although the new scheduler reduces the overhead of GPU scheduling, most applications have been designed to hide scheduling costs through buffering.

The goal of the first phase of hardware accelerated GPU scheduling is to modernize a fundamental pillar of the graphics subsystem and to set the stage for things to come… but that’s going to be a story for a another time .

We do not expect customers to experience performance regressions but if you encounter any, please be sure to file feedback at: Microsoft - Official Home Page.

Thanks

Please give this a try and let us know what you think!

Steve Pronovost,
Partner Development Lead
Click to expand...

Source: https://devblogs.microsoft.com/direc...pu-scheduling/

Buddha · Jul 7, 2020

How do I enable Hardware Acceleration?

While trying to install OS2 Warp 4 to a Virtual Machine under Virtualbox, I'm informed that it won't run because Hardware Acceleration is not enabled.

Can someone PLEASE tell me, step by step, how to do this? Show some mercy on me and don't refer me to MS articles I need an engineer to translate.

Brink · Jul 7, 2020

Bringing GPU acceleration to Windows containers

At the release of Windows Server 2019 last year, we announced support for a set of hardware devices in Windows containers. One popular type of device missing support at the time: GPUs. We’ve heard frequent feedback that you want hardware acceleration for your Windows container workloads, so today, we’re pleased to announce the first step on that journey: starting in Windows Server 2019, we now support GPU acceleration for DirectX-based apps and frameworks in Windows containers.

The best part is, you can use the Windows Server 2019 build you have today—no new OS patches or configuration is necessary. All you need is a new build of Docker and the latest display drivers. Read on for detailed requirements and to learn how you can get started with GPU accelerated DirectX in Windows containers today.

Background: Why GPU acceleration?

Containers are an excellent tool for packaging and deploying many kinds of workloads. For many of these, traditional CPU compute resources are sufficient. However, for a certain class of workload, the massively parallel compute power offered by GPUs (graphics processing units) can speed up operations by orders of magnitude, bringing down cost and improving throughput immensely.

GPUs are already a common tool for many popular workloads, from traditional rendering and simulation to machine learning training and inference. With today’s announcement, we’re unlocking new app scenarios for Windows containers and enabling more applications to be successfully shifted into Windows containers.

GPU-accelerated DirectX, Windows ML, and more

For some users, DirectX conjures associations with gaming. But DirectX is about more than games—it also powers a large ecosystem of multimedia, design, computation, and simulation frameworks and applications.

As we looked at adding GPU support to Windows containers, it was clear that starting with the DirectX APIs—the foundation of accelerated graphics, compute, and AI on Windows—was a natural first step.

By enabling GPU acceleration for DirectX, we’ve also enabled GPU acceleration for the frameworks built on top of it. One such framework is Windows ML, a set of APIs providing fast and efficient AI inferencing capabilities. With GPU acceleration in Windows containers, developers now have access to a first-class inferencing runtime that can be accelerated across a broad set of capable GPU acceleration hardware.

Usage

On a system meeting the requirements (see below), start a container with hardware-accelerated DirectX support by specifying the --device option at container runtime, as follows:

docker run --isolation process --device class/5B45201D-F2F2-4F3B-85BB-30FF1F953599 <your Docker image>

Note that this does not assign GPU resources exclusively to the container, nor does it prevent GPU access on the host. Rather, GPU resources are scheduled dynamically across the host and containers in much the same way as they are scheduled among apps running on your personal device today. You can have several Windows containers running on a host, each with hardware-accelerated DirectX capabilities.

Requirements

For this feature to work, your environment must meet the following requirements:

The container host must be running Windows Server 2019 or Windows 10, version 1809 or newer.

The container base image must be microsoft.com/windows:1809 or newer. Windows Server Core and Nano Server container images are not currently supported.

The container must be run in process isolation mode. Hyper-V isolation mode is not currently supported.

The container host must be running Docker Engine 19.03 or newer.

The container host must have a GPU running display drivers version WDDM 2.5 or newer.

To check the WDDM version of your display drivers, run the DirectX Diagnostic Tool (dxdiag.exe) on your container host. In the tool’s “Display” tab, look in the “Drivers” section as indicated below.

Getting started

Operating system support for this feature is already complete and broadly available as part of Windows Server 2019 and Windows 10, version 1809. Formal Docker support is scheduled for the upcoming Docker EE Engine 19.03 release. Until then, if you’re eager to try out the feature early, you can check out our sample on GitHub and follow the README instructions to get started. We’ll show you how to acquire a nightly build of Docker and use it to run a containerized Windows ML inferencing app with GPU acceleration.

Going forward

We look forward to getting your feedback on this experience. Please leave a comment below or tweet us with your thoughts. What are the next things you’d like to be able to do with GPU acceleration in containers on Windows?

Cheers,
Rick Manning, Graphics PM
@CraigWilhite, Windows Container PM
Click to expand...

Source: Bringing GPU acceleration to Windows containers - Microsoft Tech Community - 393939

Windows 10: How to enable Windows 10 hardware accelerated GPU scheduling

How to enable Windows 10 hardware accelerated GPU scheduling

How to enable Windows 10 hardware accelerated GPU scheduling

How to enable Windows 10 hardware accelerated GPU scheduling

How to enable Windows 10 hardware accelerated GPU scheduling - Similar Threads - enable hardware accelerated

Hardware-accelerated GPU scheduling vulnerability

Hardware-accelerated GPU scheduling vulnerability

Hardware-accelerated GPU scheduling vulnerability

hardware-accelerated gpu scheduling not showing

hardware-accelerated gpu scheduling not showing

Hardware - Accelerated GPU Scheduling not found

How to enable Hardware-accelerated GPU Scheduling in Windows 10

Hardware-Accelerated GPU Scheduling

No “Hardware accelerated GPU Scheduling” option