All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Kai Wasserbäch" <kai@dev.carbon-project.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 11/11] drm/radeon: update the VM after setting BO address v3
Date: Wed, 19 Nov 2014 14:35:09 +0100	[thread overview]
Message-ID: <546C9C8D.9060902@vodafone.de> (raw)
In-Reply-To: <546C9845.8080600@dev.carbon-project.org>

Am 19.11.2014 um 14:16 schrieb Kai Wasserbäch:
> Dear Christian,
> Christian König wrote on 19.11.2014 14:01:
>> From: Christian König <christian.koenig@amd.com>
>>
>> This way the necessary VM update is kicked off immediately
>> if all BOs involved are in GPU accessible memory.
>>
>> v2: fix vm lock
>> v3: immediately update unmaps as well
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> ---
>>   drivers/gpu/drm/radeon/radeon_gem.c | 64 +++++++++++++++++++++++++++++++++++++
>>   1 file changed, 64 insertions(+)
> Is this a fix for <http://thread.gmane.org/gmane.comp.video.dri.devel/118415>
> which I bisected to the v2 of this patch
> (<http://thread.gmane.org/gmane.comp.video.dri.devel/118415/focus=118425>) as
> present on the drm-next-3.19-wip branch?

Yes and no, it was actually the patch before this one which triggered 
the problem. The last one just made it much more likely to appear.

Please test the whole patchset on top of Dave's drm-next tree if your 
problem still exists.

Thanks,
Christian.

>
> Cheers,
> Kai
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2014-11-19 13:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 13:01 [PATCH 01/11] drm/radeon: rework vm_flush parameters Christian König
2014-11-19 13:01 ` [PATCH 02/11] drm/radeon: stop re-reserving the BO in radeon_vm_bo_set_addr Christian König
2014-11-19 13:01 ` [PATCH 03/11] drm/radeon: remove unnecessary VM syncs Christian König
2014-11-19 13:01 ` [PATCH 04/11] drm/radeon: split semaphore and sync object handling v2 Christian König
2014-11-19 13:01 ` [PATCH 05/11] drm/radeon: fence PT updates manually v2 Christian König
2014-11-19 13:01 ` [PATCH 06/11] drm/radeon: track VM update fences separately Christian König
2014-11-19 13:01 ` [PATCH 07/11] drm/radeon: use one VMID for each ring Christian König
2014-11-19 13:01 ` [PATCH 08/11] drm/radeon: fence BO_VAs manually Christian König
2014-11-19 13:01 ` [PATCH 09/11] drm/radeon: sync PD updates as shared Christian König
2014-11-19 13:01 ` [PATCH 10/11] drm/radeon: sync PT updates as shared v2 Christian König
2014-11-19 13:01 ` [PATCH 11/11] drm/radeon: update the VM after setting BO address v3 Christian König
2014-11-19 13:16   ` Kai Wasserbäch
2014-11-19 13:35     ` Christian König [this message]
2014-11-19 15:43       ` Kai Wasserbäch
2014-11-19 16:18         ` Christian König
2014-11-19 16:48           ` Kai Wasserbäch
2014-11-19 18:28 ` [PATCH 01/11] drm/radeon: rework vm_flush parameters Alex Deucher
2014-11-19 19:40   ` Christian König
2014-11-19 19:48     ` Kai Wasserbäch
2014-11-19 20:20       ` Alex Deucher

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=546C9C8D.9060902@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kai@dev.carbon-project.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.