https://bugs.freedesktop.org/show_bug.cgi?id=91037
--- Comment #8 from anonymissi...@arcor.de ---
It's clear to me that this machine wouldn't run with kde or gnome.
As I need to keep this hardware/OS combination available in an unusable state
to be able to generate the data you need to fix this
https://bugs.freedesktop.org/show_bug.cgi?id=91056
--- Comment #3 from Ilia Mirkin imir...@alum.mit.edu ---
(In reply to Béla Gyebrószki from comment #2)
The game shows the rendering issues with NV50_PROG_OPTIMIZE=1 as well.
I found that it's sufficient to change either
RUN_PASS(1,
https://bugs.freedesktop.org/show_bug.cgi?id=91056
--- Comment #2 from Béla Gyebrószki gyebr...@gmail.com ---
The game shows the rendering issues with NV50_PROG_OPTIMIZE=1 as well.
I found that it's sufficient to change either
RUN_PASS(1, CopyPropagation, run);
or
RUN_PASS(1, LoadPropagation,
If query_create fails, why would any of these functions get called?
On Mon, Jun 22, 2015 at 4:53 PM, Samuel Pitoiset
samuel.pitoi...@gmail.com wrote:
This may happen when nv50_query_create() fails to create a new query.
Signed-off-by: Samuel Pitoiset samuel.pitoi...@gmail.com
---
This commit adds support for both compute and graphics global
performance counters which have been reverse engineered with
CUPTI (Linux) and PerfKit (Windows).
Currently, only one query type can be monitored at the same time because
the Gallium's HUD doesn't fit pretty well. This will be improved
This notifier buffer object will be used to read back global performance
counters results written by the kernel.
For each domain, we will store the handle of the perfdom object, an
array of 4 counters and the number of cycles. Like the Gallium's HUD,
we keep a list of busy queries in a ring in
Signed-off-by: Samuel Pitoiset samuel.pitoi...@gmail.com
---
src/gallium/drivers/nouveau/nv50/nv50_query.c | 41 ++
src/gallium/drivers/nouveau/nv50/nv50_screen.c | 1 +
src/gallium/drivers/nouveau/nv50/nv50_screen.h | 3 ++
3 files changed, 45 insertions(+)
diff --git
Hello there,
This series exposes NVIDIA's global performance counters for Tesla through the
Gallium's HUD and the GL_AMD_performance_monitor extension.
This adds support for 24 hardware events which have been reverse engineered
with PerfKit (Windows) and CUPTI (Linux). These hardware events will
This exposes a group of global performance counters that enables
GL_AMD_performance_monitor. All piglit tests are okay.
Signed-off-by: Samuel Pitoiset samuel.pitoi...@gmail.com
---
src/gallium/drivers/nouveau/nv50/nv50_query.c | 35 ++
This may happen when nv50_query_create() fails to create a new query.
Signed-off-by: Samuel Pitoiset samuel.pitoi...@gmail.com
---
src/gallium/drivers/nouveau/nv50/nv50_query.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git
To write data at the right offset, the kernel has to know some
parameters of this ring buffer, like the number of domains and the
maximum number of queries.
Signed-off-by: Samuel Pitoiset samuel.pitoi...@gmail.com
---
src/gallium/drivers/nouveau/nv50/nv50_screen.c | 7 +++
1 file changed, 7
This will allow to monitor global performance counters through the
command stream of the GPU instead of using ioctls.
Signed-off-by: Samuel Pitoiset samuel.pitoi...@gmail.com
---
src/gallium/drivers/nouveau/nv50/nv50_screen.c | 11 +++
src/gallium/drivers/nouveau/nv50/nv50_screen.h | 1
On 06/22/2015 10:52 PM, Ilia Mirkin wrote:
If query_create fails, why would any of these functions get called?
Because the HUD doesn't check if query_create() fails and it calls other
pipe_query functions with NULL pointer instead of a valid query object.
On Mon, Jun 22, 2015 at 4:53
And an additional question: I have a trace here where a reserved bit
from CommonWord0 is set. Is that just random values that aren't
cleared by the driver, or does it have some significance? Here is the
full shader:
HEADER:
0x06040461 0 = { SPH = VTG | VERSION = 3 | KIND = VP_B |
SASS_VERSION =
https://bugs.freedesktop.org/show_bug.cgi?id=91056
Bug ID: 91056
Summary: The Bard's Tale (2005, native) has rendering issues
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity:
https://bugs.freedesktop.org/show_bug.cgi?id=90932
Marcus Moeller marcus.moel...@gmx.ch changed:
What|Removed |Added
Summary|gm105 font glitches with|gm107 font
https://bugs.freedesktop.org/show_bug.cgi?id=90932
Marcus Moeller marcus.moel...@gmx.ch changed:
What|Removed |Added
Attachment #116429|font glitches with gm105|font glitches with
https://bugs.freedesktop.org/show_bug.cgi?id=91051
Bug ID: 91051
Summary: GT650M and Nouveau - NOUVEAU(0): [drm] failed to set
drm interface version.
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=80865
--- Comment #7 from Mario Barrera mbarr...@gmx.com ---
This has been happening to me for a while, now it is more frequent, it happens
even twice a day.
Relevant parts of the log from my latest crash.
Jun 22 15:12:40 localhost kernel: nouveau E[
https://bugs.freedesktop.org/show_bug.cgi?id=91056
--- Comment #1 from Ilia Mirkin imir...@alum.mit.edu ---
Couldn't reproduce on a GF108 (nvc1), which means this is nv50-specific. I did
see some small render fail with the GF108 (the black polygon you mention
happens in the blob too), and it
https://bugs.freedesktop.org/show_bug.cgi?id=90887
--- Comment #13 from Béla Gyebrószki gyebr...@gmail.com ---
I tried the patch from comment #9 and it indeed fixed the rendering issues in
the games like Two Worlds 2, Trine: Enchanted Edition, Trine 2, XCOM:Enemy
Unknown, Stacking (running in
21 matches
Mail list logo
