From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally
unstable and poorly performing
Date: Wed, 20 Jan 2016 17:51:58 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0448761102=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 204A86E9AA
for ; Wed, 20 Jan 2016 09:52:01 -0800 (PST)
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
--===============0448761102==
Content-Type: multipart/alternative; boundary="14533123202.E0C3bD29.16862";
charset="UTF-8"
--14533123202.E0C3bD29.16862
Date: Wed, 20 Jan 2016 17:52:00 +0000
MIME-Version: 1.0
Content-Type: text/plain
https://bugs.freedesktop.org/show_bug.cgi?id=91880
--- Comment #66 from Alex Deucher ---
(In reply to Julian from comment #65)
> (In reply to Alex Deucher from comment #64)
> > (In reply to Julian from comment #63)
> > > At first I thought it was an issue with the writeback feature that caches
> > > certain register values because it also caches an rptr value that is used in
> > > the driver's gpu_lockup_check and is, to my knowledge, never actually
> > > written to.
> >
> > More likely it never gets written because the GPU has hung due to something
> > else.
>
> Sorry, I meant that I've searched the radeon source for the lines of code
> where the value was accessed from. I've only found instances of it being
> read, no instances of it being written to. But I won't put too much stock
> into that since I hardly know the code base at all. I plan to mess with the
> code a little now that I know how to compile single modules. If I find
> something substantial that this might be a bug, I'll open a new issue about
> it.
>
The gpu writes to it. The driver only reads from it. The GPU shadows the
value in system memory so that the driver doesn't have to read the register
directly.
--
You are receiving this mail because:
You are the assignee for the bug.
--14533123202.E0C3bD29.16862
Date: Wed, 20 Jan 2016 17:52:00 +0000
MIME-Version: 1.0
Content-Type: text/html
Comment # 66
on bug 91880
from Alex Deucher
(In reply to Julian from comment #65)
> (In reply to Alex Deucher from comment #64)
> > (In reply to Julian from comment #63)
> > > At first I thought it was an issue with the writeback feature that caches
> > > certain register values because it also caches an rptr value that is used in
> > > the driver's gpu_lockup_check and is, to my knowledge, never actually
> > > written to.
> >
> > More likely it never gets written because the GPU has hung due to something
> > else.
>
> Sorry, I meant that I've searched the radeon source for the lines of code
> where the value was accessed from. I've only found instances of it being
> read, no instances of it being written to. But I won't put too much stock
> into that since I hardly know the code base at all. I plan to mess with the
> code a little now that I know how to compile single modules. If I find
> something substantial that this might be a bug, I'll open a new issue about
> it.
>
The gpu writes to it. The driver only reads from it. The GPU shadows the
value in system memory so that the driver doesn't have to read the register
directly.
You are receiving this mail because:
- You are the assignee for the bug.
--14533123202.E0C3bD29.16862--
--===============0448761102==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0
cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK
--===============0448761102==--