From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 94900] HD6950 GPU lockup loop with various steam games (octodad[always], saints row 4[always], dead island[always], grid autosport[sometimes]) Date: Wed, 28 Sep 2016 17:40:46 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1374320771==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 990D36E115 for ; Wed, 28 Sep 2016 17:40:46 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1374320771== Content-Type: multipart/alternative; boundary="14750844463.dcda59cb4.7591"; charset="UTF-8" --14750844463.dcda59cb4.7591 Date: Wed, 28 Sep 2016 17:40:46 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D94900 --- Comment #29 from Marek Ol=C5=A1=C3=A1k --- (In reply to Heiko from comment #28) > @Marek, what's the best/usual way to test for performance/instruction cou= nt > in mesa changes. I noticed those 'helped'/'hurt'/'+-%' infos and some > runtime numbers in commit messages, but I don't know how they are produce= d :/ There is no way to get stats for r600g easily. Intel and radeonsi developers use their private shader-db repositories and generate their own stats. Intel have "helped/hurt +-%" stats, while we have much more detailed stats for radeonsi. --=20 You are receiving this mail because: You are the assignee for the bug.= --14750844463.dcda59cb4.7591 Date: Wed, 28 Sep 2016 17:40:46 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 29 on bug 94900<= /a> from Marek Ol=C5=A1=C3=A1k 
(In reply to Heiko from comment #28)
> @Marek, what's the best/usual way to test fo=
r performance/instruction count
> in mesa changes. I noticed those 'helped'/'hurt'/'+-%' infos and some
> runtime numbers in commit messages, but I don't know how they are prod=
uced :/

There is no way to get stats for r600g easily. Intel and radeonsi developers
use their private shader-db repositories and generate their own stats. Intel
have "helped/hurt +-%" stats, while we have much more detailed st=
ats for
radeonsi.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14750844463.dcda59cb4.7591-- --===============1374320771== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1374320771==--