linux-stable.git/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c, branch linux-4.9.y

amdkfd: Use the canonical form in branch predicates

2016-04-30T14:06:27+00:00

Found-By: Coccinelle
Signed-off-by: Edward O'Callaghan 
Signed-off-by: Oded Gabbay

drm/amdkfd: make reset wavefronts per process per device

2015-06-06T19:26:39+00:00

This commit moves the reset wavefront flag to per process per device
data structure, so we can support multiple devices.

Signed-off-by: Ben Goz 
Signed-off-by: Oded Gabbay

drm/amdkfd: Enforce kill all waves on process termination

2015-06-03T08:34:47+00:00

This commit makes sure that on process termination, after
we're destroying all the active queues, we're killing all the
existing wave front of the current process.

By doing this we're making sure that if any of the CUs were blocked
by infinite loop we're enforcing it to end the shader explicitly.

Signed-off-by: Ben Goz 
Signed-off-by: Oded Gabbay

drm/amdkfd: Add wave control operation to debugger

2015-06-03T08:33:06+00:00

The wave control operation supports several command types executed upon
existing wave fronts that belong to the currently debugged process.

The available commands are:

HALT   - Freeze wave front(s) execution
RESUME - Resume freezed wave front(s) execution
KILL   - Kill existing wave front(s)

Signed-off-by: Yair Shachar 
Signed-off-by: Oded Gabbay

drm/amdkfd: Add static user-mode queues support

2015-06-03T08:32:28+00:00

This patch adds support for static user-mode queues in QCM.
Queues which are designated as static can NOT be preempted by
the CP microcode when it is executing its scheduling algorithm.

This is needed for supporting the debugger feature, because we
can't allow the CP to preempt queues which are currently being debugged.

The number of queues that can be designated as static is limited by the
number of HQDs (Hardware Queue Descriptors).

Signed-off-by: Yair Shachar 
Signed-off-by: Oded Gabbay

Backmerge v4.1-rc4 into into drm-next

2015-05-20T06:23:53+00:00

We picked up a silent conflict in amdkfd with drm-fixes and drm-next,
backmerge v4.1-rc5 and fix the conflicts

Signed-off-by: Dave Airlie 

Conflicts:
	drivers/gpu/drm/drm_irq.c

drm/amdkfd: Add interrupt handling module

2015-05-19T09:13:39+00:00

This patch adds the interrupt handling module, kfd_interrupt.c, and its
related members in different data structures to the amdkfd driver.

The amdkfd interrupt module maintains an internal interrupt ring
per amdkfd device. The internal interrupt ring contains interrupts
that needs further handling. The extra handling is deferred to
a later time through a workqueue.

There's no acknowledgment for the interrupts we use. The hardware
simply queues a new interrupt each time without waiting.

The fixed-size internal queue means that it's possible for us to lose
interrupts because we have no back-pressure to the hardware.

However, only interrupts that are "wanted" by amdkfd, are copied into
the amdkfd s/w interrupt ring, in order to minimize the chances
for overflow of the ring.

Signed-off-by: Andrew Lewycky 
Signed-off-by: Oded Gabbay

drm/amdkfd: make the sdma vm init to be asic specific

2015-05-19T09:13:39+00:00

Signed-off-by: Oded Gabbay 
Reviewed-by: Alex Deucher

drm/amdkfd: Initialize sdma vm when creating sdma queue

2015-05-07T14:38:06+00:00

This patch fixes a bug where sdma vm wasn't initialized when
an sdma queue was created in HWS mode.

This caused GPUVM faults to appear on dmesg and it is one of the
causes that SDMA queues are not working.

Signed-off-by: Xihan Zhang 
Reviewed-by: Ben Goz 
Signed-off-by: Oded Gabbay 
Cc: stable@vger.kernel.org
Reviewed-by: Alex Deucher

drm/amdkfd: allow unregister process with queues

2015-05-07T14:37:41+00:00

Sometimes we might unregister process that have queues, because we couldn't
preempt the queues. Until now we blocked it with BUG_ON but instead just
print it as debug.

Reviewed-by: Ben Goz 
Signed-off-by: Oded Gabbay 
Cc: stable@vger.kernel.org
Reviewed-by: Alex Deucher