From: "Christian König" <deathsimple@vodafone.de>
To: Dave Airlie <airlied@gmail.com>
Cc: Jerome Glisse <jglisse@redhat.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: fix possible lack of synchronization btw ttm and other ring
Date: Fri, 04 May 2012 10:48:04 +0200 [thread overview]
Message-ID: <4FA397C4.3060509@vodafone.de> (raw)
In-Reply-To: <CAPM=9tz1oDMcmn2Q-Cje-WHi82UMv=tqugRDx_Ra7xmYME6AnA@mail.gmail.com>
On 04.05.2012 10:42, Dave Airlie wrote:
>>> From: Jerome Glisse<jglisse@redhat.com>
>>>
>>> We need to sync with the GFX ring as ttm might have schedule bo move
>>> on it and new command scheduled for other ring need to wait for bo
>>> data to be in place.
>>>
> Is this required for -fixes? if so it doesn't apply clean.
Nope, only drm-next, since there isn't any public available client that
makes use of it.
Christian.
prev parent reply other threads:[~2012-05-04 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 17:44 [PATCH] drm/radeon: fix possible lack of synchronization btw ttm and other ring j.glisse
2012-05-03 18:25 ` Alex Deucher
2012-05-04 7:58 ` Christian König
2012-05-04 8:42 ` Dave Airlie
2012-05-04 8:48 ` 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=4FA397C4.3060509@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
/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