All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Marek Olšák" <maraeo@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/radeon: stop poisoning the GART TLB
Date: Wed, 11 Jun 2014 11:29:46 +0200	[thread overview]
Message-ID: <5398218A.4040104@vodafone.de> (raw)
In-Reply-To: <CAAxE2A6eZW4yhCao3y0PKTMoh_=Qm+ckkRb5ZYdsR4_cWcNgwQ@mail.gmail.com>

Crap, I already wanted to check back with you if that really fixes your 
problems.

Thanks for the info, this crash also only happens on CIK doesn't it?

Christian.

Am 11.06.2014 01:30, schrieb Marek Olšák:
> Sorry to tell you the bad news. This patch doesn't fix the hangs on my machine.
>
> I tested drm-next-3.16 from Alex's tree. I also switched copying from
> SDMA to CP DMA, which hung too.
>
> I also tried this:
>
> git checkout (the problematic commit):
> 6d2f294 - drm/radeon: use normal BOs for the page tables v4
>
> git cherry-pick (fixes):
> 0e97703c - drm/radeon: add define for flags used in R600+ GTT
> 0986c1a5 - drm/radeon: stop poisoning the GART TLB
> 4906f689 - drm/radeon: fix page directory update size estimation
> 4b095566 - drm/radeon: fix buffer placement under memory pressure v2
>
> Then I tested both SDMA and CP DMA copying. Both were unstable.
>
> Testing was done with piglit / quick.tests.
>
> Marek
>
>
> On Wed, Jun 4, 2014 at 3:29 PM, Christian König <deathsimple@vodafone.de> wrote:
>> From: Christian König <christian.koenig@amd.com>
>>
>> When we set the valid bit on invalid GART entries they are
>> loaded into the TLB when an adjacent entry is loaded. This
>> poisons the TLB with invalid entries which are sometimes
>> not correctly removed on TLB flush.
>>
>> For stable inclusion the patch probably needs to be modified a bit.
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Cc: stable@vger.kernel.org
>> ---
>>   drivers/gpu/drm/radeon/rs600.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/radeon/rs600.c b/drivers/gpu/drm/radeon/rs600.c
>> index 0a8be63..e0465b2 100644
>> --- a/drivers/gpu/drm/radeon/rs600.c
>> +++ b/drivers/gpu/drm/radeon/rs600.c
>> @@ -634,7 +634,10 @@ int rs600_gart_set_page(struct radeon_device *rdev, int i, uint64_t addr)
>>                  return -EINVAL;
>>          }
>>          addr = addr & 0xFFFFFFFFFFFFF000ULL;
>> -       addr |= R600_PTE_GART;
>> +       if (addr == rdev->dummy_page.addr)
>> +               addr |= R600_PTE_SYSTEM | R600_PTE_SNOOPED;
>> +       else
>> +               addr |= R600_PTE_GART;
>>          writeq(addr, ptr + (i * 8));
>>          return 0;
>>   }
>> --
>> 1.9.1
>>
>> _______________________________________________
>> 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

  reply	other threads:[~2014-06-11  9:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 13:29 [PATCH 1/3] drm/radeon: stop poisoning the GART TLB Christian König
2014-06-04 13:29 ` [PATCH 2/3] drm/radeon: remove range check from *_gart_set_page Christian König
2014-06-04 13:29 ` [PATCH 3/3] drm/radeon: use the SDMA on for buffer moves on CIK again Christian König
2014-06-04 13:46 ` [PATCH 1/3] drm/radeon: stop poisoning the GART TLB Alex Deucher
2014-06-04 13:50   ` Christian König
2014-06-10 23:30 ` Marek Olšák
2014-06-11  9:29   ` Christian König [this message]
2014-06-11 10:56     ` Marek Olšák
2014-06-12 11:23       ` Christian König
2014-06-13 13:19         ` Marek Olšák
2014-06-13 15:45           ` Christian König
2014-06-13 21:31             ` Alex Deucher
2014-06-15 12:48               ` Christian König
2014-06-19  1:48                 ` Michel Dänzer
2014-06-19  9:45                   ` Christian König
2014-06-23  8:15                     ` Michel Dänzer
2014-06-23  9:56                       ` Christian König
2014-06-24  6:49                         ` Michel Dänzer
2014-06-24 10:14                           ` Christian König
2014-06-25  3:59                             ` Michel Dänzer
2014-06-26 12:25                               ` Dieter Nützel
2014-06-27  2:31                               ` Michel Dänzer
2014-06-27  8:26                                 ` Christian König
2014-06-27  8:59                                   ` Michel Dänzer
2014-06-29 10:34                                     ` Christian König
2014-06-30  6:10                                       ` Michel Dänzer
2014-06-30  7:43                                         ` Christian König
2014-07-01  6:48                                           ` Michel Dänzer
2014-07-01 12:16                                             ` Christian König
2014-07-02  6:57                                               ` Michel Dänzer
2014-07-02 19:31                                                 ` Christian König
2014-07-03  3:48                                                   ` Michel Dänzer
2014-07-03  6:36                                                     ` Christian König
2014-06-19 10:20                   ` Marek Olšák
2014-06-19 10:25                     ` Christian König
2014-06-20  1:10                     ` Michel Dänzer

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=5398218A.4040104@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maraeo@gmail.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 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.