From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84648] Lag/Pause When VRAM->GTT or GTT->VRAM transfer occur
Date: Sun, 15 Mar 2015 21:56:56 +0000 [thread overview]
Message-ID: <bug-84648-502-eHeMJeNkoO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84648-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 467 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=84648
--- Comment #15 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to J0k3r from comment #14)
> Alex, as I understand it these kernel changes are just going to make it into
> 4.1. That's a long time in the future. Will the fixes be backported to
> 3.19/4.0?
They were applied to 4.0 and they will also show up in the stable kernels.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1330 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:[~2015-03-15 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 4:17 [Bug 84648] New: Lag/Pause When VRAM->GTT or GTT->VRAM transfer occur bugzilla-daemon
2014-10-04 4:18 ` [Bug 84648] " bugzilla-daemon
2014-10-06 9:13 ` bugzilla-daemon
2014-12-25 17:59 ` bugzilla-daemon
2015-01-28 20:50 ` bugzilla-daemon
2015-01-28 20:51 ` bugzilla-daemon
2015-02-02 22:02 ` bugzilla-daemon
2015-02-03 12:37 ` bugzilla-daemon
2015-02-06 2:34 ` bugzilla-daemon
2015-02-26 16:18 ` bugzilla-daemon
2015-03-14 17:11 ` bugzilla-daemon
2015-03-14 17:15 ` bugzilla-daemon
2015-03-14 17:19 ` bugzilla-daemon
2015-03-14 17:20 ` bugzilla-daemon
2015-03-14 17:39 ` bugzilla-daemon
2015-03-15 21:56 ` bugzilla-daemon [this message]
2015-05-01 21:56 ` 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-84648-502-eHeMJeNkoO@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 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.