[pull] amdgpu drm-fixes-4.14

[Alex Deucher]

Hi Dave,

Just two small patches for suspend/resume regressions.

The following changes since commit 2cb3a34abd035756f9ba3cde12f44f4b3e4c234b:

  Merge tag 'drm-intel-fixes-2017-10-18-1' of 
git://anongit.freedesktop.org/drm/drm-intel into drm-fixes (2017-10-19 15:00:47 
+1000)

are available in the git repository at:

  git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14

for you to fetch changes up to d3daa2c7865cbfa830651b11c8ad1df23465b46e:

  drm/amd/amdgpu: Remove workaround check for UVD6 on APUs (2017-10-25 09:32:14 
-0400)


Rex Zhu (1):
  drm/amd/powerplay: fix uninitialized variable

Tom St Denis (1):
  drm/amd/amdgpu: Remove workaround check for UVD6 on APUs

 drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c| 16 +---
 drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c |  6 +++---
 2 files changed, 8 insertions(+), 14 deletions(-)
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [pull] amdgpu drm-fixes-4.14

[Christian König]

Am 18.10.2017 um 18:58 schrieb Deucher, Alexander:

-Original Message-
From: Michel Dänzer [mailto:mic...@daenzer.net]
Sent: Wednesday, October 18, 2017 12:06 PM
To: Koenig, Christian; Alex Deucher
Cc: Deucher, Alexander; Dave Airlie; amd-gfx list; Maling list - DRI developers
Subject: Re: [pull] amdgpu drm-fixes-4.14

On 13/10/17 10:19 AM, Christian König wrote:

Am 13.10.2017 um 09:41 schrieb Michel Dänzer:

On 12/10/17 07:49 PM, Alex Deucher wrote:

On Thu, Oct 12, 2017 at 1:02 PM, Christian König
<ckoenig.leichtzumer...@gmail.com> wrote:

Am 12.10.2017 um 18:20 schrieb Michel Dänzer:

On 12/10/17 05:58 PM, Alex Deucher wrote:

Hi Dave,

One memory management regression fix.

The following changes since commit
545036a9944e9d6e50fed4ca03117147c880ff71:

 Merge tag 'drm-misc-fixes-2017-10-11' of
git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-

10-12

10:38:09 +1000)

are available in the git repository at:

 git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14

for you to fetch changes up to
27b94b4f1386c3a8181f5a0277434a32e24e7dd7:

 drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-

12

10:34:42 -0400)


Christian König (1):
 drm/amdgpu: fix placement flags in amdgpu_ttm_bind

Thanks Alex, but there's another piglit hang regression in 4.14,
caused
by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
amd-staging-drm-next. Either the latter need to be backported to

4.14,

or the former needs to be reverted from it.

The revert is probably easier to handle at this point.

So to answer your question from the other thread I vote for that.

Nicolai's patches apply cleanly and I think they change about the same
amount of code and we don't have to worry about any problems down

the

road when the revert gets merged into drm-next.

That's basically why I asked which way to go. However, Monk just
reported a potential regression in one of Nicolai's changes, so
reverting seems safer for 4.14.

I agree that reverting the original offending patch is probably the
better approach.

Alex, are you planning to send a pull request for the revert? Let me
know if there's anything I can do to help.


Yeah, I'll send it out shortly.


Sorry for the delay. I wanted to send a revert on Monday, but somehow 
forgot it over the weekend. Thanks for taking care of this Alex.


Christian.



Alex



--
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx



___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

[pull] amdgpu drm-fixes-4.14

[Alex Deucher]

Hi Dave,

Just one revert to fix a stability regression.

The following changes since commit 2de0307323fc42c6395d0eafec9879d55e042c85:

  Merge tag 'exynos-drm-fixes-for-v4.14-rc5' of 
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-fixes 
(2017-10-17 10:14:56 +1000)

are available in the git repository at:

  git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14

for you to fetch changes up to c94501279bb191ccf204f496e9576ce036f81bcd:

  Revert "drm/amdgpu: discard commands of killed processes" (2017-10-18 
12:57:47 -0400)


Alex Deucher (1):
  Revert "drm/amdgpu: discard commands of killed processes"

 drivers/gpu/drm/amd/scheduler/gpu_scheduler.c | 23 ---
 1 file changed, 4 insertions(+), 19 deletions(-)
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

RE: [pull] amdgpu drm-fixes-4.14

[Deucher, Alexander]

> -Original Message-
> From: Michel Dänzer [mailto:mic...@daenzer.net]
> Sent: Wednesday, October 18, 2017 12:06 PM
> To: Koenig, Christian; Alex Deucher
> Cc: Deucher, Alexander; Dave Airlie; amd-gfx list; Maling list - DRI 
> developers
> Subject: Re: [pull] amdgpu drm-fixes-4.14
> 
> On 13/10/17 10:19 AM, Christian König wrote:
> > Am 13.10.2017 um 09:41 schrieb Michel Dänzer:
> >> On 12/10/17 07:49 PM, Alex Deucher wrote:
> >>> On Thu, Oct 12, 2017 at 1:02 PM, Christian König
> >>> <ckoenig.leichtzumer...@gmail.com> wrote:
> >>>> Am 12.10.2017 um 18:20 schrieb Michel Dänzer:
> >>>>> On 12/10/17 05:58 PM, Alex Deucher wrote:
> >>>>>> Hi Dave,
> >>>>>>
> >>>>>> One memory management regression fix.
> >>>>>>
> >>>>>> The following changes since commit
> >>>>>> 545036a9944e9d6e50fed4ca03117147c880ff71:
> >>>>>>
> >>>>>>     Merge tag 'drm-misc-fixes-2017-10-11' of
> >>>>>> git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-
> 10-12
> >>>>>> 10:38:09 +1000)
> >>>>>>
> >>>>>> are available in the git repository at:
> >>>>>>
> >>>>>>     git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14
> >>>>>>
> >>>>>> for you to fetch changes up to
> >>>>>> 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:
> >>>>>>
> >>>>>>     drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-
> 12
> >>>>>> 10:34:42 -0400)
> >>>>>>
> >>>>>> 
> >>>>>> Christian König (1):
> >>>>>>     drm/amdgpu: fix placement flags in amdgpu_ttm_bind
> >>>>> Thanks Alex, but there's another piglit hang regression in 4.14,
> >>>>> caused
> >>>>> by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
> >>>>> processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
> >>>>> amd-staging-drm-next. Either the latter need to be backported to
> 4.14,
> >>>>> or the former needs to be reverted from it.
> >>>>
> >>>> The revert is probably easier to handle at this point.
> >>>>
> >>>> So to answer your question from the other thread I vote for that.
> >>> Nicolai's patches apply cleanly and I think they change about the same
> >>> amount of code and we don't have to worry about any problems down
> the
> >>> road when the revert gets merged into drm-next.
> >> That's basically why I asked which way to go. However, Monk just
> >> reported a potential regression in one of Nicolai's changes, so
> >> reverting seems safer for 4.14.
> >
> > I agree that reverting the original offending patch is probably the
> > better approach.
> 
> Alex, are you planning to send a pull request for the revert? Let me
> know if there's anything I can do to help.


Yeah, I'll send it out shortly.

Alex

> 
> 
> --
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [pull] amdgpu drm-fixes-4.14

[Michel Dänzer]

On 13/10/17 10:19 AM, Christian König wrote:
> Am 13.10.2017 um 09:41 schrieb Michel Dänzer:
>> On 12/10/17 07:49 PM, Alex Deucher wrote:
>>> On Thu, Oct 12, 2017 at 1:02 PM, Christian König
>>>  wrote:
 Am 12.10.2017 um 18:20 schrieb Michel Dänzer:
> On 12/10/17 05:58 PM, Alex Deucher wrote:
>> Hi Dave,
>>
>> One memory management regression fix.
>>
>> The following changes since commit
>> 545036a9944e9d6e50fed4ca03117147c880ff71:
>>
>>     Merge tag 'drm-misc-fixes-2017-10-11' of
>> git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-10-12
>> 10:38:09 +1000)
>>
>> are available in the git repository at:
>>
>>     git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14
>>
>> for you to fetch changes up to
>> 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:
>>
>>     drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-12
>> 10:34:42 -0400)
>>
>> 
>> Christian König (1):
>>     drm/amdgpu: fix placement flags in amdgpu_ttm_bind
> Thanks Alex, but there's another piglit hang regression in 4.14,
> caused
> by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
> processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
> amd-staging-drm-next. Either the latter need to be backported to 4.14,
> or the former needs to be reverted from it.

 The revert is probably easier to handle at this point.

 So to answer your question from the other thread I vote for that.
>>> Nicolai's patches apply cleanly and I think they change about the same
>>> amount of code and we don't have to worry about any problems down the
>>> road when the revert gets merged into drm-next.
>> That's basically why I asked which way to go. However, Monk just
>> reported a potential regression in one of Nicolai's changes, so
>> reverting seems safer for 4.14.
> 
> I agree that reverting the original offending patch is probably the
> better approach.

Alex, are you planning to send a pull request for the revert? Let me
know if there's anything I can do to help.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [pull] amdgpu drm-fixes-4.14

[Christian König]

Am 13.10.2017 um 09:41 schrieb Michel Dänzer:

On 12/10/17 07:49 PM, Alex Deucher wrote:

On Thu, Oct 12, 2017 at 1:02 PM, Christian König
 wrote:

Am 12.10.2017 um 18:20 schrieb Michel Dänzer:

On 12/10/17 05:58 PM, Alex Deucher wrote:

Hi Dave,

One memory management regression fix.

The following changes since commit
545036a9944e9d6e50fed4ca03117147c880ff71:

Merge tag 'drm-misc-fixes-2017-10-11' of
git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-10-12
10:38:09 +1000)

are available in the git repository at:

git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14

for you to fetch changes up to 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:

drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-12
10:34:42 -0400)


Christian König (1):
drm/amdgpu: fix placement flags in amdgpu_ttm_bind

Thanks Alex, but there's another piglit hang regression in 4.14, caused
by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
amd-staging-drm-next. Either the latter need to be backported to 4.14,
or the former needs to be reverted from it.


The revert is probably easier to handle at this point.

So to answer your question from the other thread I vote for that.

Nicolai's patches apply cleanly and I think they change about the same
amount of code and we don't have to worry about any problems down the
road when the revert gets merged into drm-next.

That's basically why I asked which way to go. However, Monk just
reported a potential regression in one of Nicolai's changes, so
reverting seems safer for 4.14.


I agree that reverting the original offending patch is probably the 
better approach.


Regards,
Christian.
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [pull] amdgpu drm-fixes-4.14

[Michel Dänzer]

On 12/10/17 07:49 PM, Alex Deucher wrote:
> On Thu, Oct 12, 2017 at 1:02 PM, Christian König
>  wrote:
>> Am 12.10.2017 um 18:20 schrieb Michel Dänzer:
>>> On 12/10/17 05:58 PM, Alex Deucher wrote:

 Hi Dave,

 One memory management regression fix.

 The following changes since commit
 545036a9944e9d6e50fed4ca03117147c880ff71:

Merge tag 'drm-misc-fixes-2017-10-11' of
 git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-10-12
 10:38:09 +1000)

 are available in the git repository at:

git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14

 for you to fetch changes up to 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:

drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-12
 10:34:42 -0400)

 
 Christian König (1):
drm/amdgpu: fix placement flags in amdgpu_ttm_bind
>>>
>>> Thanks Alex, but there's another piglit hang regression in 4.14, caused
>>> by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
>>> processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
>>> amd-staging-drm-next. Either the latter need to be backported to 4.14,
>>> or the former needs to be reverted from it.
>>
>>
>> The revert is probably easier to handle at this point.
>>
>> So to answer your question from the other thread I vote for that.
> 
> Nicolai's patches apply cleanly and I think they change about the same
> amount of code and we don't have to worry about any problems down the
> road when the revert gets merged into drm-next.

That's basically why I asked which way to go. However, Monk just
reported a potential regression in one of Nicolai's changes, so
reverting seems safer for 4.14.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [pull] amdgpu drm-fixes-4.14

[Alex Deucher]

On Thu, Oct 12, 2017 at 1:02 PM, Christian König
 wrote:
> Am 12.10.2017 um 18:20 schrieb Michel Dänzer:
>>
>> On 12/10/17 05:58 PM, Alex Deucher wrote:
>>>
>>> Hi Dave,
>>>
>>> One memory management regression fix.
>>>
>>> The following changes since commit
>>> 545036a9944e9d6e50fed4ca03117147c880ff71:
>>>
>>>Merge tag 'drm-misc-fixes-2017-10-11' of
>>> git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-10-12
>>> 10:38:09 +1000)
>>>
>>> are available in the git repository at:
>>>
>>>git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14
>>>
>>> for you to fetch changes up to 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:
>>>
>>>drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-12
>>> 10:34:42 -0400)
>>>
>>> 
>>> Christian König (1):
>>>drm/amdgpu: fix placement flags in amdgpu_ttm_bind
>>
>> Thanks Alex, but there's another piglit hang regression in 4.14, caused
>> by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
>> processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
>> amd-staging-drm-next. Either the latter need to be backported to 4.14,
>> or the former needs to be reverted from it.
>
>
> The revert is probably easier to handle at this point.
>
> So to answer your question from the other thread I vote for that.

Nicolai's patches apply cleanly and I think they change about the same
amount of code and we don't have to worry about any problems down the
road when the revert gets merged into drm-next.

Alex
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [pull] amdgpu drm-fixes-4.14

[Christian König]

Am 12.10.2017 um 18:20 schrieb Michel Dänzer:

On 12/10/17 05:58 PM, Alex Deucher wrote:

Hi Dave,

One memory management regression fix.

The following changes since commit 545036a9944e9d6e50fed4ca03117147c880ff71:

   Merge tag 'drm-misc-fixes-2017-10-11' of 
git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-10-12 10:38:09 
+1000)

are available in the git repository at:

   git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14

for you to fetch changes up to 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:

   drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-12 10:34:42 
-0400)


Christian König (1):
   drm/amdgpu: fix placement flags in amdgpu_ttm_bind

Thanks Alex, but there's another piglit hang regression in 4.14, caused
by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
amd-staging-drm-next. Either the latter need to be backported to 4.14,
or the former needs to be reverted from it.


The revert is probably easier to handle at this point.

So to answer your question from the other thread I vote for that.

Christian.

___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

RE: [pull] amdgpu drm-fixes-4.14

[Deucher, Alexander]

> -Original Message-
> From: Michel Dänzer [mailto:mic...@daenzer.net]
> Sent: Thursday, October 12, 2017 12:21 PM
> To: Alex Deucher
> Cc: amd-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
> airl...@gmail.com; Deucher, Alexander
> Subject: Re: [pull] amdgpu drm-fixes-4.14
> 
> On 12/10/17 05:58 PM, Alex Deucher wrote:
> > Hi Dave,
> >
> > One memory management regression fix.
> >
> > The following changes since commit
> 545036a9944e9d6e50fed4ca03117147c880ff71:
> >
> >   Merge tag 'drm-misc-fixes-2017-10-11' of
> git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-10-12
> 10:38:09 +1000)
> >
> > are available in the git repository at:
> >
> >   git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14
> >
> > for you to fetch changes up to
> 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:
> >
> >   drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-12
> 10:34:42 -0400)
> >
> > 
> > Christian König (1):
> >   drm/amdgpu: fix placement flags in amdgpu_ttm_bind
> 
> Thanks Alex, but there's another piglit hang regression in 4.14, caused
> by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
> processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
> amd-staging-drm-next. Either the latter need to be backported to 4.14,
> or the former needs to be reverted from it.

Sorting that out seemed like more effort, so I opted to just send this out.  
Once we get that fixed up, I can send another fixes pull.

Alex

___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [pull] amdgpu drm-fixes-4.14

[Michel Dänzer]

On 12/10/17 05:58 PM, Alex Deucher wrote:
> Hi Dave,
> 
> One memory management regression fix.
> 
> The following changes since commit 545036a9944e9d6e50fed4ca03117147c880ff71:
> 
>   Merge tag 'drm-misc-fixes-2017-10-11' of 
> git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-10-12 
> 10:38:09 +1000)
> 
> are available in the git repository at:
> 
>   git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14
> 
> for you to fetch changes up to 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:
> 
>   drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-12 10:34:42 
> -0400)
> 
> 
> Christian König (1):
>   drm/amdgpu: fix placement flags in amdgpu_ttm_bind

Thanks Alex, but there's another piglit hang regression in 4.14, caused
by commit 6af0883ed977 "drm/amdgpu: discard commands of killed
processes", fixed by five commits 6b37d03280a4..318d85de9c20 in
amd-staging-drm-next. Either the latter need to be backported to 4.14,
or the former needs to be reverted from it.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

[pull] amdgpu drm-fixes-4.14

[Alex Deucher]

Hi Dave,

One memory management regression fix.

The following changes since commit 545036a9944e9d6e50fed4ca03117147c880ff71:

  Merge tag 'drm-misc-fixes-2017-10-11' of 
git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2017-10-12 10:38:09 
+1000)

are available in the git repository at:

  git://people.freedesktop.org/~agd5f/linux drm-fixes-4.14

for you to fetch changes up to 27b94b4f1386c3a8181f5a0277434a32e24e7dd7:

  drm/amdgpu: fix placement flags in amdgpu_ttm_bind (2017-10-12 10:34:42 -0400)


Christian König (1):
  drm/amdgpu: fix placement flags in amdgpu_ttm_bind

 drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx