From: "Michel Dänzer" <michel@daenzer.net>
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: Fri, 20 Jun 2014 10:10:46 +0900 [thread overview]
Message-ID: <53A38A16.8050208@daenzer.net> (raw)
In-Reply-To: <CAAxE2A4D9YAXs7Ly3JUh5yvo8ksFMmMCgs9RxL+BuY2uR1V49w@mail.gmail.com>
On 19.06.2014 19:20, Marek Olšák wrote:
> Hi Michel,
>
> 3.15 doesn't contain Christian's fix yet, so it should be always
> broken for everybody. The fix is currently only in 3.16.
>
> Alternatively, you can cherry-pick the fix to 3.15, but it doesn't
> apply cleanly.
That's a good point. Sorry, I should have mentioned I've been testing
with the GART poisoning fix backported to 3.15.
> There is a workaround in 3.15 which disables sDMA and uses CP DMA for
> copying buffers. It seems to help Christian's machine, but not mine.
I've been testing with CP DMA on Bonaire FWIW.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2014-06-20 1:10 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
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 [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=53A38A16.8050208@daenzer.net \
--to=michel@daenzer.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox