Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Tomáš Trnka" <trnka@scm.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"sashal@kernel.org" <sashal@kernel.org>,
	"Yu, Lang" <Lang.Yu@amd.com>,
	"Kuehling, Felix" <Felix.Kuehling@amd.com>
Subject: Re: [PATCH] drm/amdkfd: handle duplicate BOs in reserve_bo_and_cond_vms
Date: Thu, 13 Jun 2024 10:14:30 +0200	[thread overview]
Message-ID: <2024061357-unseemly-nervy-7b25@gregkh> (raw)
In-Reply-To: <26439120.1r3eYUQgxm@mintaka.ncbr.muni.cz>

On Thu, Jun 13, 2024 at 10:04:51AM +0200, Tomáš Trnka wrote:
> On Wednesday, June 12, 2024 2:06:37 PM CEST, Greg KH wrote:
> > On Mon, Jun 03, 2024 at 02:31:27PM +0000, Deucher, Alexander wrote:
> > > [Public]
> > > 
> > > > -----Original Message-----
> > > > From: Greg KH <gregkh@linuxfoundation.org>
> > > > Sent: Saturday, June 1, 2024 1:24 AM
> > > > To: Deucher, Alexander <Alexander.Deucher@amd.com>
> > > > Cc: stable@vger.kernel.org; sashal@kernel.org; Yu, Lang
> > > > <Lang.Yu@amd.com>;
> > > > Tomáš Trnka <trnka@scm.com>; Kuehling, Felix <Felix.Kuehling@amd.com>
> > > > Subject: Re: [PATCH] drm/amdkfd: handle duplicate BOs in
> > > > reserve_bo_and_cond_vms
> > > > 
> > > > On Fri, May 31, 2024 at 10:18:07AM -0400, Alex Deucher wrote:
> > > > > From: Lang Yu <Lang.Yu@amd.com>
> > > > > 
> > > > > Observed on gfx8 ASIC where
> > > > 
> > > > KFD_IOC_ALLOC_MEM_FLAGS_AQL_QUEUE_MEM is used.
> > > > 
> > > > > Two attachments use the same VM, root PD would be locked twice.
> > > > > 
> > > > > [   57.910418] Call Trace:
> > > > > [   57.793726]  ? reserve_bo_and_cond_vms+0x111/0x1c0 [amdgpu]
> > > > > [   57.793820]
> > > > 
> > > > amdgpu_amdkfd_gpuvm_unmap_memory_from_gpu+0x6c/0x1c0 [amdgpu]
> > > > 
> > > > > [   57.793923]  ? idr_get_next_ul+0xbe/0x100
> > > > > [   57.793933]  kfd_process_device_free_bos+0x7e/0xf0 [amdgpu]
> > > > > [   57.794041]  kfd_process_wq_release+0x2ae/0x3c0 [amdgpu]
> > > > > [   57.794141]  ? process_scheduled_works+0x29c/0x580
> > > > > [   57.794147]  process_scheduled_works+0x303/0x580
> > > > > [   57.794157]  ? __pfx_worker_thread+0x10/0x10
> > > > > [   57.794160]  worker_thread+0x1a2/0x370
> > > > > [   57.794165]  ? __pfx_worker_thread+0x10/0x10
> > > > > [   57.794167]  kthread+0x11b/0x150
> > > > > [   57.794172]  ? __pfx_kthread+0x10/0x10
> > > > > [   57.794177]  ret_from_fork+0x3d/0x60
> > > > > [   57.794181]  ? __pfx_kthread+0x10/0x10
> > > > > [   57.794184]  ret_from_fork_asm+0x1b/0x30
> > > > > 
> > > > > Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3007
> > > > > Tested-by: Tomáš Trnka <trnka@scm.com>
> > > > > Signed-off-by: Lang Yu <Lang.Yu@amd.com>
> > > > > Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>
> > > > > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > > > > Cc: stable@vger.kernel.org
> > > > > (cherry picked from commit
> > > > 
> > > > 2a705f3e49d20b59cd9e5cc3061b2d92ebe1e5f0)
> > > > 
> > > > > ---
> > > > > 
> > > > >  drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 3 ++-
> > > > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > > 
> > > > What kernel release(s) is this backport for?
> > > 
> > > 6.6.x and newer.
> > 
> > Does not apply to 6.6.y, sorry, how was this tested?  Can you submit a
> > patch that does work?
> > 
> > thanks,
> > 
> > greg k-h
> 
> Sorry about that. 6.6 does not have commit 
> 05d249352f1ae909230c230767ca8f4e9fdf8e7b "drm/exec: Pass in initial # of 
> objects" which adds the trailing 0 argument. Just removing that zero makes the 
> patch apply and work. Such a modified version is attached below.
> 
> Tested on 6.6.32 (version below), 6.8.12 and 6.9.3 (version sent by Alex 
> above).
> 
> 2T
> 
> From: Lang Yu <Lang.Yu@amd.com>
> 
> Observed on gfx8 ASIC where KFD_IOC_ALLOC_MEM_FLAGS_AQL_QUEUE_MEM is used.
> Two attachments use the same VM, root PD would be locked twice.
> 
> [   57.910418] Call Trace:
> [   57.793726]  ? reserve_bo_and_cond_vms+0x111/0x1c0 [amdgpu]
> [   57.793820]  amdgpu_amdkfd_gpuvm_unmap_memory_from_gpu+0x6c/0x1c0 [amdgpu]
> [   57.793923]  ? idr_get_next_ul+0xbe/0x100
> [   57.793933]  kfd_process_device_free_bos+0x7e/0xf0 [amdgpu]
> [   57.794041]  kfd_process_wq_release+0x2ae/0x3c0 [amdgpu]
> [   57.794141]  ? process_scheduled_works+0x29c/0x580
> [   57.794147]  process_scheduled_works+0x303/0x580
> [   57.794157]  ? __pfx_worker_thread+0x10/0x10
> [   57.794160]  worker_thread+0x1a2/0x370
> [   57.794165]  ? __pfx_worker_thread+0x10/0x10
> [   57.794167]  kthread+0x11b/0x150
> [   57.794172]  ? __pfx_kthread+0x10/0x10
> [   57.794177]  ret_from_fork+0x3d/0x60
> [   57.794181]  ? __pfx_kthread+0x10/0x10
> [   57.794184]  ret_from_fork_asm+0x1b/0x30
> 
> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3007
> Tested-by: Tomáš Trnka <trnka@scm.com>
> Signed-off-by: Lang Yu <Lang.Yu@amd.com>
> Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> Cc: stable@vger.kernel.org
> (cherry picked from commit 2a705f3e49d20b59cd9e5cc3061b2d92ebe1e5f0)

As you are modifying, and passing on, a patch, you need to also sign off
on this.

Please submit this in a format that I can apply it in, not as something
I need to hand-edit out of an email.

thanks,

greg k-h

  reply	other threads:[~2024-06-13  8:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 14:18 [PATCH] drm/amdkfd: handle duplicate BOs in reserve_bo_and_cond_vms Alex Deucher
2024-06-01  5:24 ` Greg KH
2024-06-03 14:31   ` Deucher, Alexander
2024-06-12 12:06     ` Greg KH
2024-06-13  8:04       ` Tomáš Trnka
2024-06-13  8:14         ` Greg KH [this message]
2024-06-13  8:36           ` Tomáš Trnka
2024-06-13  8:50             ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024061357-unseemly-nervy-7b25@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Alexander.Deucher@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=Lang.Yu@amd.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trnka@scm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox