From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103100] Performance regression with various games in drm-next-amd-staging Kernel
Date: Sat, 02 Dec 2017 19:32:50 +0000 [thread overview]
Message-ID: <bug-103100-502-mySL5tmP4g@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103100-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 493 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103100
--- Comment #10 from Gregor Münch <gr.muench@gmail.com> ---
Ive updated test, with staging kernel and mesa from today:
https://openbenchmarking.org/result/1712028-AL-GAMETEST322
Looks like I enabled performance governor by accident. But overall 4.11 is
still faster- so it looks like there were some performance improvements in mesa
in the last days.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1397 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-12-02 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 16:38 [Bug 103100] Image corruptions, instability and performance regression in drm-next-wip Kernel bugzilla-daemon
2017-10-12 6:52 ` bugzilla-daemon
2017-10-15 18:57 ` bugzilla-daemon
2017-11-21 20:35 ` [Bug 103100] Performance regression with various games in drm-next-amd-staging Kernel bugzilla-daemon
2017-11-22 10:40 ` bugzilla-daemon
2017-11-22 11:42 ` bugzilla-daemon
2017-11-22 11:56 ` bugzilla-daemon
2017-11-22 20:58 ` bugzilla-daemon
2017-11-22 20:59 ` bugzilla-daemon
2017-11-22 21:02 ` bugzilla-daemon
2017-12-02 19:32 ` bugzilla-daemon [this message]
2017-12-12 13:02 ` bugzilla-daemon
2017-12-12 19:51 ` 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-103100-502-mySL5tmP4g@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.