Re: [PATCH 1/9] drm/amdgpu: make sure BOs are locked in amdgpu_vm_get_memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/16/23 14:16, Greg KH wrote:
On Fri, Jul 07, 2023 at 11:07:26AM -0400, Alex Deucher wrote:
From: Christian König <christian.koenig@xxxxxxx>

We need to grab the lock of the BO or otherwise can run into a crash
when we try to inspect the current location.

Signed-off-by: Christian König <christian.koenig@xxxxxxx>
Reviewed-by: Alex Deucher <alexander.deucher@xxxxxxx>
Acked-by: Guchun Chen <guchun.chen@xxxxxxx>
Tested-by: Mikhail Gavrilov <mikhail.v.gavrilov@xxxxxxxxx>
Signed-off-by: Alex Deucher <alexander.deucher@xxxxxxx>
(cherry picked from commit e2ad8e2df432498b1cee2af04df605723f4d75e6)
Cc: stable@xxxxxxxxxxxxxxx # 6.3.x
---
  drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 69 +++++++++++++++-----------
  1 file changed, 39 insertions(+), 30 deletions(-)

I've applied the first 7 patches here to 6.4.y, which I am guessing is
where you want them applied to, yet you didn't really say?

The last 2 did not apply :(

And some of these should go into 6.1.y also?  Please send a patch series
and give me a hint as to where they should be applied to next time so I
don't have to guess...

thanks,

greg k-h

In this case the individual patches with specific requirements have:

Cc: stable@xxxxxxxxxxxxxxx # version

They were sent before 6.3 went EOL, so here is the updated summary from them:
6.4.y:
1, 2, 3, 4, 5, 6, 7, 8, 9

6.1.y:
3, 4, 5, 6, 7, 8, 9

3 is particularly important for 6.1.y as we have active regressions reported related to it on 6.1.y.

So can you please take 3-7 to 6.1.y and I'll look more closely at what is wrong with 8 and 9 on 6.1.y and 6.4.y and resend them?





[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux