From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82050] R9270X pyrit benchmark perf regressions with latest kernel/llvm
Date: Thu, 02 Oct 2014 18:48:31 +0000 [thread overview]
Message-ID: <bug-82050-502-5dOMzzf8T5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82050-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1138 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=82050
--- Comment #75 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Christoph Haag from comment #74)
> Well.
>
> I have said that I used drm-next-3.18 and had these hangs.
> When I applied
> http://lists.freedesktop.org/archives/mesa-dev/2014-August/066746.html it
> did not help.
>
> Now I am using 3.17-rc7 with that mesa patch and I do not see these hangs
> anymore. Or maybe they are these very short stutters.
>
> Sorry if drm-next-3.18 behavior is not relevant here.
>
> As for the num bytes moved: Does the HUD graph only accumulate everything
> that happened in the hang? If so, then the hundreds of megabytes still seem
> more than normal and the used graphs definitely show change before and after
> the hangs. Whatever you make of that...
>
>
> CONFIG_CMA is not enabled on either kernel.
>
> Indeed, there's less moving of data with the rc kernel I think.
> For comparison: https://www.youtube.com/watch?v=mFaqHGle9Hg
It would be useful to know if Elemental also worked with 3.17-rc7.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2209 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:[~2014-10-02 18:48 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 12:04 [Bug 82050] New: R9270X pyrit benchmark perf regressions with latest kernel/llvm bugzilla-daemon
2014-08-04 15:57 ` [Bug 82050] " bugzilla-daemon
2014-08-05 9:40 ` bugzilla-daemon
2014-08-05 15:21 ` bugzilla-daemon
2014-08-05 16:02 ` bugzilla-daemon
2014-08-05 16:22 ` bugzilla-daemon
2014-08-05 17:21 ` bugzilla-daemon
2014-08-05 17:22 ` bugzilla-daemon
2014-08-05 23:23 ` bugzilla-daemon
2014-08-12 9:03 ` bugzilla-daemon
2014-08-12 11:47 ` bugzilla-daemon
2014-08-13 9:11 ` bugzilla-daemon
2014-08-13 15:08 ` bugzilla-daemon
2014-08-14 1:22 ` bugzilla-daemon
2014-08-14 11:51 ` bugzilla-daemon
2014-08-14 18:24 ` bugzilla-daemon
2014-08-14 20:28 ` bugzilla-daemon
2014-08-19 7:15 ` bugzilla-daemon
2014-08-19 18:32 ` bugzilla-daemon
2014-08-19 22:06 ` bugzilla-daemon
2014-08-19 22:22 ` bugzilla-daemon
2014-08-27 7:16 ` bugzilla-daemon
2014-08-27 7:16 ` bugzilla-daemon
2014-08-27 7:18 ` bugzilla-daemon
2014-08-27 8:07 ` bugzilla-daemon
2014-08-27 8:45 ` bugzilla-daemon
2014-08-27 18:42 ` bugzilla-daemon
2014-08-28 6:59 ` bugzilla-daemon
2014-08-28 9:01 ` bugzilla-daemon
2014-08-28 12:19 ` bugzilla-daemon
2014-08-28 17:50 ` bugzilla-daemon
2014-08-29 1:01 ` bugzilla-daemon
2014-09-01 6:23 ` bugzilla-daemon
2014-09-01 7:11 ` bugzilla-daemon
2014-09-01 9:16 ` bugzilla-daemon
2014-09-01 9:54 ` bugzilla-daemon
2014-09-01 9:58 ` bugzilla-daemon
2014-09-01 9:59 ` bugzilla-daemon
2014-09-01 10:09 ` bugzilla-daemon
2014-09-01 11:59 ` bugzilla-daemon
2014-09-01 12:59 ` bugzilla-daemon
2014-09-01 13:20 ` bugzilla-daemon
2014-09-01 14:33 ` bugzilla-daemon
2014-09-01 14:36 ` bugzilla-daemon
2014-09-01 14:37 ` bugzilla-daemon
2014-09-01 14:59 ` bugzilla-daemon
2014-09-02 9:20 ` bugzilla-daemon
2014-09-02 9:28 ` bugzilla-daemon
2014-09-02 10:44 ` bugzilla-daemon
2014-09-02 11:06 ` bugzilla-daemon
2014-09-02 11:55 ` bugzilla-daemon
2014-09-02 12:43 ` bugzilla-daemon
2014-09-02 22:25 ` bugzilla-daemon
2014-09-02 23:39 ` bugzilla-daemon
2014-09-03 10:08 ` bugzilla-daemon
2014-09-03 14:04 ` bugzilla-daemon
2014-09-03 15:26 ` bugzilla-daemon
2014-09-30 8:14 ` bugzilla-daemon
2014-09-30 8:38 ` bugzilla-daemon
2014-09-30 10:52 ` bugzilla-daemon
2014-09-30 13:32 ` bugzilla-daemon
2014-10-01 1:36 ` bugzilla-daemon
2014-10-01 11:54 ` bugzilla-daemon
2014-10-01 11:55 ` bugzilla-daemon
2014-10-01 13:37 ` bugzilla-daemon
2014-10-01 14:12 ` bugzilla-daemon
2014-10-01 14:14 ` bugzilla-daemon
2014-10-01 14:24 ` bugzilla-daemon
2014-10-01 14:27 ` bugzilla-daemon
2014-10-01 15:36 ` bugzilla-daemon
2014-10-01 15:58 ` bugzilla-daemon
2014-10-01 16:04 ` bugzilla-daemon
2014-10-02 7:11 ` bugzilla-daemon
2014-10-02 7:17 ` bugzilla-daemon
2014-10-02 11:14 ` bugzilla-daemon
2014-10-02 18:48 ` bugzilla-daemon [this message]
2014-10-02 18:54 ` bugzilla-daemon
2014-10-02 21:28 ` bugzilla-daemon
2014-10-04 15:00 ` bugzilla-daemon
2014-10-10 1:29 ` bugzilla-daemon
2014-10-10 15:23 ` 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-82050-502-5dOMzzf8T5@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.