From: "Christian König" <deathsimple@vodafone.de>
To: "Alex Deucher" <alexdeucher@gmail.com>,
"Michel Dänzer" <michel@daenzer.net>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/radeon: Always flush VM again on < CIK
Date: Fri, 15 Aug 2014 16:52:30 +0200 [thread overview]
Message-ID: <53EE1EAE.6050601@vodafone.de> (raw)
In-Reply-To: <53E9D8EF.7000907@vodafone.de>
Hey guys,
I think I've figured out what the cause of the remaining issues is while
working on the implicit sync stuff.
The issue happens when the flush is done because of a CS to the DMA ring
and a CS to the GFX ring directly after that which depends on the DMA
submission to be finished.
In this situation we insert semaphore command so that the GFX ring wait
for the DMA ring to finish execution and normally don't flush on the GFX
ring a second time (the flush should be done on the DMA ring and we
waited for that to finish).
The problem here is that semaphores can't be executed on the PFP, so the
PFP doesn't wait for the semaphore to be completed and happily starts
fetching commands while the flush on the DMA ring isn't completed.
@Michel: can you give this branch a try and see if it now works for you:
http://cgit.freedesktop.org/~deathsimple/linux/log/?h=vm-flushing
We should keep that behavior in mind should we switch to put IBs into
normal BOs, cause when those a swapped out the synchronization won't
wait for swapping them back in using the DMA as well.
Thanks,
Christian.
Am 12.08.2014 um 11:05 schrieb Christian König:
> Am 11.08.2014 um 17:00 schrieb Alex Deucher:
>> On Mon, Aug 11, 2014 at 4:42 AM, Michel Dänzer <michel@daenzer.net>
>> wrote:
>>> On 08.08.2014 22:34, Alex Deucher wrote:
>>>> On Fri, Aug 8, 2014 at 9:31 AM, Alex Deucher
>>>> <alexdeucher@gmail.com> wrote:
>>>>> On Fri, Aug 8, 2014 at 4:50 AM, Michel Dänzer <michel@daenzer.net>
>>>>> wrote:
>>>>>> On 08.08.2014 17:44, Christian König wrote:
>>>>>>>>>> On Thu, Aug 7, 2014 at 3:59 PM, Alex Deucher
>>>>>>>>>> <alexdeucher@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>> We should be using PFP as much as possible. Does the attached
>>>>>>>>>>> patch help?
>>>>>>>> Unfortunately not.
>>>>>>> Maybe add a readback of the VM base addr pointer to make sure
>>>>>>> that the
>>>>>>> write has really reached the SBRM?
>>>>>> I'm not sure what exactly you're thinking of, but I'm happy to
>>>>>> test any
>>>>>> patches you guys come up with. :)
>>>>>>
>>>>> Maybe some variant of this patch?
>>>> Ignore that one. typo. Try this one instead.
>>> Thanks, but still no luck.
>> I'm out of ideas at the moment. I'll apply your patch unless
>> Christian can think of anything else.
>
> Unfortunately not, so apply the patch for now.
>
> Christian.
>
>>
>> Alex
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-08-15 14:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 7:46 [PATCH] drm/radeon: Always flush VM again on < CIK Michel Dänzer
2014-08-07 13:59 ` Alex Deucher
2014-08-07 15:38 ` Marek Olšák
2014-08-07 15:47 ` Christian König
2014-08-07 15:55 ` Alex Deucher
2014-08-08 2:38 ` Michel Dänzer
2014-08-08 8:44 ` Christian König
2014-08-08 8:50 ` Michel Dänzer
2014-08-08 13:31 ` Alex Deucher
2014-08-08 13:34 ` Alex Deucher
2014-08-11 8:42 ` Michel Dänzer
2014-08-11 15:00 ` Alex Deucher
2014-08-12 9:05 ` Christian König
2014-08-15 14:52 ` Christian König [this message]
2014-08-18 9:10 ` Michel Dänzer
2014-08-18 9:44 ` Christian König
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=53EE1EAE.6050601@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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.