[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-20 Thread Zhu, Rex
Deucher; amd-gfx list; Maling list - DRI developers Subject: RE: [PATCH] drm/amd/powerplay: don't give up if DPM is already running Hi Gražvydas, Sorry for so late response. I can reproduce this issue in gpu passthrough case. When we forced power off the VM or forced reset the VM without

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-19 Thread Zhu, Rex
: Alex Deucher; amd-gfx list; Maling list - DRI developers Subject: Re: [PATCH] drm/amd/powerplay: don't give up if DPM is already running Hi, On Thu, Oct 13, 2016 at 10:45 AM, Zhu, Rex wrote: > > The attached patches were also for this issue. > Disable dpm when rmmod amdgpu. It works for

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-15 Thread Grazvydas Ignotas
Hi, On Thu, Oct 13, 2016 at 10:45 AM, Zhu, Rex wrote: > > The attached patches were also for this issue. > Disable dpm when rmmod amdgpu. It works for modprobe-rmmod-modprobe test, thanks. However with GPU passthrough (giving control of the GPU to a Windows virtual machine using iommu, then

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-14 Thread Deucher, Alexander
; Cc: Grazvydas Ignotas; amd-gfx list; Maling list - DRI developers > Subject: Re: [PATCH] drm/amd/powerplay: don't give up if DPM is already > running > > On Thu, Oct 13, 2016 at 3:45 AM, Zhu, Rex wrote: > > Hi all, > > > > The attached patches were also for this is

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-14 Thread Zhu, Rex
: Grazvydas Ignotas; amd-gfx list; Maling list - DRI developers Subject: Re: [PATCH] drm/amd/powerplay: don't give up if DPM is already running On Thu, Oct 13, 2016 at 3:45 AM, Zhu, Rex wrote: > Hi all, > > The attached patches were also for this issue. > Disable dpm when rmmod amdgpu. >

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-13 Thread Alex Deucher
sk. > > Best Regards > Rex > > -Original Message- > From: Alex Deucher [mailto:alexdeucher at gmail.com] > Sent: Wednesday, October 12, 2016 4:01 AM > To: Grazvydas Ignotas; Zhu, Rex > Cc: Maling list - DRI developers; amd-gfx list > Subject: Re: [PATCH] drm/amd/po

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-13 Thread Zhu, Rex
Deucher; Grazvydas Ignotas Cc: amd-gfx list; Maling list - DRI developers Subject: RE: [PATCH] drm/amd/powerplay: don't give up if DPM is already running Hi Grazvydas and Alex, We needed to disable dpm when rmmod amdgpu for this issue. I am checking the function of disable dpm task. Best Regards Rex

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-12 Thread Zhu, Rex
, Rex Cc: Maling list - DRI developers; amd-gfx list Subject: Re: [PATCH] drm/amd/powerplay: don't give up if DPM is already running +Rex to review this. Alex On Sun, Oct 9, 2016 at 3:23 PM, Grazvydas Ignotas wrote: > Currently the driver crashes if smu7_enable_dpm_tasks() returns ea

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-11 Thread Alex Deucher
+Rex to review this. Alex On Sun, Oct 9, 2016 at 3:23 PM, Grazvydas Ignotas wrote: > Currently the driver crashes if smu7_enable_dpm_tasks() returns early, > which it does if DPM is already active. It seems to be better just to > continue anyway, at least I haven't noticed any ill effects. It's

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-10 Thread Edward O'Callaghan
Reviewed-by: Edward O'Callaghan On 10/10/2016 06:23 AM, Grazvydas Ignotas wrote: > Currently the driver crashes if smu7_enable_dpm_tasks() returns early, > which it does if DPM is already active. It seems to be better just to > continue anyway, at least I haven't noticed any ill effects. It's

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

2016-10-09 Thread Grazvydas Ignotas
Currently the driver crashes if smu7_enable_dpm_tasks() returns early, which it does if DPM is already active. It seems to be better just to continue anyway, at least I haven't noticed any ill effects. It's also unclear at what state the hardware was left by the previous driver, so IMO it's better