All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
Cc: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 1/2] drm/amdgpu: fix prime teardown order
Date: Fri, 9 Mar 2018 15:07:21 +0100	[thread overview]
Message-ID: <083be9c1-d3e7-ea5a-c5ad-453002f844ef@gmail.com> (raw)
In-Reply-To: <d0c896ef-de5f-ff95-ea2b-14eb51064c4d-otUistvHUpPR7s880joybQ@public.gmane.org>

Am 09.03.2018 um 15:05 schrieb Michel Dänzer:
> On 2018-03-09 02:46 PM, Christian König wrote:
>> We unmapped imported DMA-bufs when the GEM handle was dropped, not when the
>> hardware was done with the buffere.
> Good catch! I guess that explains some oddities I sometimes saw with
> PRIME. Both patches are

Yeah and it took me a month to hunt that down. Thanks to IOMMU or 
otherwise I wouldn't have even noticed that something is wrong.

> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>

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

      parent reply	other threads:[~2018-03-09 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 13:46 [PATCH 1/2] drm/amdgpu: fix prime teardown order Christian König
     [not found] ` <20180309134604.2390-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-03-09 13:46   ` [PATCH 2/2] drm/radeon: " Christian König
2018-03-09 14:05   ` [PATCH 1/2] drm/amdgpu: " Michel Dänzer
     [not found]     ` <d0c896ef-de5f-ff95-ea2b-14eb51064c4d-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-03-09 14:07       ` Christian König [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=083be9c1-d3e7-ea5a-c5ad-453002f844ef@gmail.com \
    --to=ckoenig.leichtzumerken-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=michel-otUistvHUpPR7s880joybQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.