dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: "Alex Deucher" <alexdeucher@gmail.com>,
	"Christian König" <deathsimple@vodafone.de>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/radeon: take exclusive_lock in read mode during ring tests
Date: Mon, 18 Aug 2014 22:02:13 +0200	[thread overview]
Message-ID: <53F25BC5.7060706@canonical.com> (raw)
In-Reply-To: <CADnq5_P0G=XsAp5w3rn=VhB542O0D71=8x7=wuvoBvu0MG6gUQ@mail.gmail.com>

Hey,

On 18-08-14 18:10, Alex Deucher wrote:
> On Mon, Aug 18, 2014 at 12:07 PM, Christian König
> <deathsimple@vodafone.de> wrote:
>>> Yeah, looks like a bug.  I think the attached patch should fix it.
>>
>> Sounds logical and the patch is Reviewed-by: Christian König
>> <christian.koenig@amd.com>
>>
>> Going to apply Maartens patch on top and test that one a bit to make sure it
>> works as expected.
> 
> pushed my current -fixes queue to my drm-fixes-3.17-wip branch if that helps.

Thanks, maybe that fixes uvd on resume for me. :-)

I'll have to rework it to include the changes, but does resuming everything in the order of my v2 patch look sane?
Then as a final act I'm downgrading to read, and run the tests.

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

  reply	other threads:[~2014-08-18 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 14:45 [PATCH 1/3] drm/radeon: take exclusive_lock in read mode during ring tests Maarten Lankhorst
2014-08-18 14:45 ` [PATCH 2/3] drm/radeon: handle lockup in delayed work, v3 Maarten Lankhorst
2014-08-18 15:12   ` Christian König
2014-08-18 15:28     ` Maarten Lankhorst
2014-08-18 16:20       ` Christian König
2014-08-18 14:46 ` [PATCH 3/3] drm/radeon: add timeout argument to radeon_fence_wait_seq Maarten Lankhorst
2014-08-18 15:02 ` [PATCH 1/3] drm/radeon: take exclusive_lock in read mode during ring tests Christian König
2014-08-18 15:24   ` [PATCH 1/3] drm/radeon: take exclusive_lock in read mode during ring tests, v2 Maarten Lankhorst
2014-08-18 16:03   ` [PATCH 1/3] drm/radeon: take exclusive_lock in read mode during ring tests Alex Deucher
2014-08-18 16:07     ` Christian König
2014-08-18 16:10       ` Alex Deucher
2014-08-18 20:02         ` Maarten Lankhorst [this message]
2014-08-18 20:56           ` 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=53F25BC5.7060706@canonical.com \
    --to=maarten.lankhorst@canonical.com \
    --cc=alexdeucher@gmail.com \
    --cc=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.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