From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 26345] [845G] CPU/GPU incoherency
Date: Mon, 17 Dec 2012 15:38:29 +0000 [thread overview]
Message-ID: <bug-26345-502-9h64ZMHxxx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-26345-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1232 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=26345
--- Comment #153 from Chris Wilson <chris@chris-wilson.co.uk> ---
Now in kernel form as well:
commit b75e53bac7f4164e1c53a636352faa3d177b4beb
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Sun Dec 16 18:08:07 2012 +0100
drm/i915: Implement workaround for broken CS tlb on i830/845
Now that Chris Wilson demonstrated that the key for stability on early
gen 2 is to simple _never_ exchange the physical backing storage of
batch buffers I've tried a stab at a kernel solution. Doesn't look too
nefarious imho, now that I don't try to be too clever for my own good
any more.
v2: After discussing the various techniques, we've decided to always blit
batches on the suspect devices, but allow userspace to opt out of the
kernel workaround assume full responsibility for providing coherent
batches. The principal reason is that avoiding the blit does improve
performance in a few key microbenchmarks and also in cairo-trace
replays.
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2186 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-12-17 15:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-26345-502@http.bugs.freedesktop.org/>
2011-09-08 22:55 ` [Bug 26345] [845G] CPU/GPU incoherency bugzilla-daemon
2011-09-09 9:11 ` bugzilla-daemon
2011-09-20 13:00 ` bugzilla-daemon
2011-11-01 22:04 ` bugzilla-daemon
2011-11-06 16:44 ` bugzilla-daemon
2011-12-08 18:35 ` bugzilla-daemon
2012-04-14 13:37 ` bugzilla-daemon
2012-04-14 13:41 ` bugzilla-daemon
2012-04-14 14:45 ` bugzilla-daemon
2012-04-16 11:27 ` bugzilla-daemon
2012-07-22 1:09 ` bugzilla-daemon
2012-08-03 12:18 ` bugzilla-daemon
2012-08-26 19:24 ` bugzilla-daemon
2012-09-03 2:14 ` bugzilla-daemon
2012-10-12 17:25 ` bugzilla-daemon
2012-11-09 20:23 ` bugzilla-daemon
2012-11-20 18:26 ` bugzilla-daemon
2012-12-12 20:54 ` bugzilla-daemon
2012-12-17 15:38 ` bugzilla-daemon [this message]
2013-02-26 22:51 ` bugzilla-daemon
2013-02-27 0:12 ` bugzilla-daemon
2013-02-27 15:46 ` bugzilla-daemon
2013-03-05 22:03 ` bugzilla-daemon
2013-03-06 9:08 ` bugzilla-daemon
2013-04-30 1:36 ` bugzilla-daemon
2013-04-30 5:46 ` bugzilla-daemon
2017-07-14 14:10 ` bugzilla-daemon
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=bug-26345-502-9h64ZMHxxx@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--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