public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
	stable@vger.kernel.org,
	"Christian König" <christian.koenig@amd.com>,
	"Guchun Chen" <guchun.chen@amd.com>,
	"Mikhail Gavrilov" <mikhail.v.gavrilov@gmail.com>
Subject: Re: [PATCH 1/9] drm/amdgpu: make sure BOs are locked in amdgpu_vm_get_memory
Date: Sun, 16 Jul 2023 21:28:29 +0200	[thread overview]
Message-ID: <2023071654-flattery-fidgety-0e31@gregkh> (raw)
In-Reply-To: <bfb99ba9-8fb3-1af7-d0b2-c617bbd5c2b6@amd.com>

On Sun, Jul 16, 2023 at 02:22:36PM -0500, Mario Limonciello wrote:
> 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@amd.com>
> > > 
> > > 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@amd.com>
> > > Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> > > Acked-by: Guchun Chen <guchun.chen@amd.com>
> > > Tested-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
> > > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > > (cherry picked from commit e2ad8e2df432498b1cee2af04df605723f4d75e6)
> > > Cc: stable@vger.kernel.org # 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@vger.kernel.org # 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?

I can't really pick out these for 6.1 from the larger series as I'm
drowning in patches at the moment.  Please send a backported series and
I'll be glad to queue that up.

thanks,

greg k-h

      reply	other threads:[~2023-07-16 19:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 15:07 [PATCH 1/9] drm/amdgpu: make sure BOs are locked in amdgpu_vm_get_memory Alex Deucher
2023-07-07 15:07 ` [PATCH 2/9] drm/amdgpu: make sure that BOs have a backing store Alex Deucher
2023-07-07 15:07 ` [PATCH 3/9] drm/amdgpu: Skip mark offset for high priority rings Alex Deucher
2023-07-07 15:07 ` [PATCH 4/9] drm/amd/pm: revise the ASPM settings for thunderbolt attached scenario Alex Deucher
2023-07-07 15:07 ` [PATCH 5/9] drm/amdgpu/sdma4: set align mask to 255 Alex Deucher
2023-07-07 15:07 ` [PATCH 6/9] drm/amd/pm: add abnormal fan detection for smu 13.0.0 Alex Deucher
2023-07-07 15:07 ` [PATCH 7/9] drm/amdgpu: check RAS irq existence for VCN/JPEG Alex Deucher
2023-07-07 15:07 ` [PATCH 8/9] drm/amdgpu: fix number of fence calculations Alex Deucher
2023-07-07 15:07 ` [PATCH 9/9] drm/amd: Don't try to enable secure display TA multiple times Alex Deucher
2023-07-11 21:40 ` [PATCH 1/9] drm/amdgpu: make sure BOs are locked in amdgpu_vm_get_memory Mario Limonciello
2023-07-12  5:12   ` Greg Kroah-Hartman
2023-07-16 19:16 ` Greg KH
2023-07-16 19:22   ` Mario Limonciello
2023-07-16 19:28     ` Greg KH [this message]

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=2023071654-flattery-fidgety-0e31@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=guchun.chen@amd.com \
    --cc=mario.limonciello@amd.com \
    --cc=mikhail.v.gavrilov@gmail.com \
    --cc=stable@vger.kernel.org \
    /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