From: "Christian König" <deathsimple@vodafone.de>
To: alexdeucher@gmail.com
Cc: dri-devel@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
Jerome Glisse <jglisse@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: Always flush the VM
Date: Tue, 16 Apr 2013 19:45:52 +0200 [thread overview]
Message-ID: <516D8E50.3000508@vodafone.de> (raw)
In-Reply-To: <1366129569-8059-1-git-send-email-alexdeucher@gmail.com>
Am 16.04.2013 18:26, schrieb alexdeucher@gmail.com:
> From: Jerome Glisse <jglisse@redhat.com>
>
> This is slightly cleaned up version of Jerome's patch.
> There seems to be an issue tracking the last flush of
> the VM which results in hangs in certain cases when
> VM is used. For now just flush the VM for every IB.
>
> Fixes:
> https://bugs.freedesktop.org/show_bug.cgi?id=62959
> https://bugs.freedesktop.org/show_bug.cgi?id=62997
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/radeon/radeon_ring.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_ring.c b/drivers/gpu/drm/radeon/radeon_ring.c
> index 31e47d8..e17faa7 100644
> --- a/drivers/gpu/drm/radeon/radeon_ring.c
> +++ b/drivers/gpu/drm/radeon/radeon_ring.c
> @@ -180,7 +180,8 @@ int radeon_ib_schedule(struct radeon_device *rdev, struct radeon_ib *ib,
> radeon_semaphore_free(rdev, &ib->semaphore, NULL);
> }
> /* if we can't remember our last VM flush then flush now! */
> - if (ib->vm && !ib->vm->last_flush) {
> + /* XXX figure out why we have to flush for every IB */
> + if (ib->vm /*&& !ib->vm->last_flush*/) {
> radeon_ring_vm_flush(rdev, ib->ring, ib->vm);
> }
> if (const_ib) {
prev parent reply other threads:[~2013-04-16 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 16:26 [PATCH] drm/radeon: Always flush the VM alexdeucher
2013-04-16 17:45 ` 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=516D8E50.3000508@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.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