Hello everyone. My name is Adarsh Khubchandani and I am an engineering student
from Mumbai, India. I have pretty decent knowledge of C, Java, Python, HTML,
CSS as well as technical documentation. My question is how to get started as a
contributor and apply for EVOC. The directions given on the s
Hello Gurchetan,
On Wed, 27 Feb 2019 10:34:26 -0800
Gurchetan Singh wrote:
> On Mon, Feb 25, 2019 at 12:35 AM Boris Brezillon
> wrote:
> >
> > From: Daniel Stone
> >
> > pipe_boxes are x/y + width/height, rather than x0/y0 -> x1/y1. This
> > means that (x+width) is not included in the box.
> >
https://bugs.freedesktop.org/show_bug.cgi?id=109741
--- Comment #2 from Gert Wollny ---
There is a patch for this:
https://patchwork.freedesktop.org/patch/225706/
--
You are receiving this mail because:
You are the QA Contact for the bug.___
mesa-dev
Am Mi., 27. Feb. 2019 um 17:12 Uhr schrieb Alyssa Rosenzweig
:
>
> > super nitpicking: What is the purpose of this change? Should this
> > define be added when it really gets used?
>
> I mean, we don't have explicit documentation on the cmdstream; if I
> don't add the define / enum / struct / whate
On Tue, 2019-02-26 at 18:34 -0500, Marek Olšák wrote:
> I ran a simple test verifying that compute is working properly on the
> compute ring.
I guess this was not on raven? With his patch I no loner see gfx
timeout but the apps still hang. anyway that's a separate issue.
>
> When clover is using
https://bugs.freedesktop.org/show_bug.cgi?id=109443
--- Comment #8 from Jose Fonseca ---
(In reply to Alex Granni from comment #7)
> I'd go for this way as 3.0.4 is also affected.
OK. I'll assume I have your Tested-By and post it for review.
--
You are receiving this mail because:
You are the
Hi
On Thu, Feb 28, 2019 at 1:17 AM Marek Olšák wrote:
>
> I'd rather have something more robust than an env var, like catching SIGSYS.
With current qemu in most distros, it defaults to SIGSYS (we switched
away from SCMP_ACT_KILL, which had other problems). With more recent
qemu/libseccomp, it wi
This change applies the workaround suggested by Bill Deegan on the
affected SCons versions.
It also adds a comment with the URL explaining why we were using
customizing the decider and max_drift in the first place, as I had
forgotten all about it.
Bugzilla: https://bugs.freedesktop.org/show_bug.c
Hi Adarsh,
On Thu, 28 Feb 2019 at 08:32, Adarsh Khubchandani wrote:
>
> Hello everyone. My name is Adarsh Khubchandani and I am an engineering
> student from Mumbai, India. I have pretty decent knowledge of C, Java,
> Python, HTML, CSS as well as technical documentation. My question is how to
On Tue, 26 Feb 2019 at 21:52, Chris Wilson wrote:
>
> A few of the GEM drivers provide matching ioctls to allow control of
> their bo caches. Hook these up to APPLE_object_purgeable to allow
> clients to discard video memory under pressure where they are able to
> fallback to restoring content the
Quoting Emil Velikov (2019-02-28 11:44:28)
> On Tue, 26 Feb 2019 at 21:52, Chris Wilson wrote:
> >
> > A few of the GEM drivers provide matching ioctls to allow control of
> > their bo caches. Hook these up to APPLE_object_purgeable to allow
> > clients to discard video memory under pressure where
On Wed, 27 Feb 2019 at 22:49, Axel Davy wrote:
>
> Check GetWindowInfo and ignore the computed sizes
> if there is an error.
>
> Fixes the regression caused by:
> commit 2318ca68bbeb4fa6e21a4d8c650cec3f64246596
> "st/nine: Handle window resize when a presentation buffer is used"
> when using old w
Hi,
On 28.2.2019 11.57, Marc-André Lureau wrote:
On Thu, Feb 28, 2019 at 1:17 AM Marek Olšák wrote:
I'd rather have something more robust than an env var, like catching SIGSYS.
SIGSYS is info for the invoking parent, not the (Mesa) process doing the
syscall.
From "man 2 seccomp":
The pro
On Wed, 2019-02-27 at 17:04 -0800, Ian Romanick wrote:
> On 2/27/19 4:45 AM, Iago Toral Quiroga wrote:
> > Now that we propagate constants to the first source of 2src
> > instructions we
> > see more opportunities of constant folding in the backend.
> >
> > Shader-db results on KBL:
> >
> > total
https://bugs.freedesktop.org/show_bug.cgi?id=109535
Timo Aaltonen changed:
What|Removed |Added
Depends on||109695
Referenced Bugs:
https://bugs.
On Tue, 19 Feb 2019 at 16:00, Eric Engestrom wrote:
>
> On Tuesday, 2019-02-19 14:08:08 +, Emil Velikov wrote:
> > From: Emil Velikov
> >
> > VGEM and kms_swrast were introduced to work with one another.
> >
> > All we do is CPU rendering to dumb buffers. There is no reason to carve
> > out G
https://bugs.freedesktop.org/show_bug.cgi?id=109532
--- Comment #50 from asimiklit ---
(In reply to Ian Romanick from comment #49)
> After discussing https://github.com/KhronosGroup/OpenGL-API/issues/46 in the
> Khronos call today, I realized that my thinking about this bug may have been
> slight
Hi Eero!
(ex-colleagues, long time ago!)
On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen wrote:
>
> Hi,
>
> On 28.2.2019 11.57, Marc-André Lureau wrote:
> > On Thu, Feb 28, 2019 at 1:17 AM Marek Olšák wrote:
> >> I'd rather have something more robust than an env var, like catching
> >> SIGSYS.
>
https://bugs.freedesktop.org/show_bug.cgi?id=109791
--- Comment #3 from asimiklit ---
I suggested a patch to add the warning:
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/358
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
Hi,
Just catching up on this thread now. My main question is where is issue
occurring? Is it some sort of CI system or something along those lines? We
don't really consider SWR in an emulated environment to be an intended use
case. Generally it is used as the rendering backend for data visualiz
https://bugs.freedesktop.org/show_bug.cgi?id=109535
Bug 109535 depends on bug 109055, which changed state.
Bug 109055 Summary: ~10% perf drop in Sascha Willems Vulkan Multithreading demo
https://bugs.freedesktop.org/show_bug.cgi?id=109055
What|Removed |Added
---
Iago Toral writes:
> On Wed, 2019-02-27 at 15:44 -0800, Francisco Jerez wrote:
>> Iago Toral Quiroga writes:
>>
>> > The section 'Execution Data Types' of 3D Media GPGPU volume, which
>> > describes execution types, is exactly the same in BDW and SKL+.
>> >
>> > Also, this section states that
Iago Toral writes:
> On Wed, 2019-02-27 at 13:47 -0800, Francisco Jerez wrote:
>> Iago Toral writes:
>>
>> > On Tue, 2019-02-26 at 14:54 -0800, Francisco Jerez wrote:
>> > > Iago Toral Quiroga writes:
>> > >
>> > > > ---
>> > > > src/intel/compiler/brw_eu_validate.c| 64 -
>>
Am 28.02.19 um 11:03 schrieb Jose Fonseca:
> This change applies the workaround suggested by Bill Deegan on the
> affected SCons versions.
>
> It also adds a comment with the URL explaining why we were using
> customizing the decider and max_drift in the first place, as I had
> forgotten all about
On 28/02/2019 12:54, Emil Velikov wrote:
On Wed, 27 Feb 2019 at 22:49, Axel Davy wrote:
Check GetWindowInfo and ignore the computed sizes
if there is an error.
Fixes the regression caused by:
commit 2318ca68bbeb4fa6e21a4d8c650cec3f64246596
"st/nine: Handle window resize when a presentation buf
https://bugs.freedesktop.org/show_bug.cgi?id=109535
Dylan Baker changed:
What|Removed |Added
Depends on|109131 |
Referenced Bugs:
https://bugs.freedesk
https://bugs.freedesktop.org/show_bug.cgi?id=109131
Dylan Baker changed:
What|Removed |Added
Blocks|109535 |
--- Comment #5 from Dylan Baker ---
I h
On 02/28/2019 03:03 AM, Jose Fonseca wrote:
This change applies the workaround suggested by Bill Deegan on the
affected SCons versions.
It also adds a comment with the URL explaining why we were using
customizing the decider and max_drift in the first place, as I had
forgotten all about it.
Bug
On Thu, Feb 28, 2019 at 11:13 AM Marc-André Lureau <
marcandre.lur...@gmail.com> wrote:
> Hi Eero!
>
> (ex-colleagues, long time ago!)
>
> On Thu, Feb 28, 2019 at 1:37 PM Eero Tamminen
> wrote:
> >
> > Hi,
> >
> > On 28.2.2019 11.57, Marc-André Lureau wrote:
> > > On Thu, Feb 28, 2019 at 1:17 AM
https://bugs.freedesktop.org/show_bug.cgi?id=109803
Bug ID: 109803
Summary: page not found is showing
Product: Mesa
Version: 7.4
Hardware: Other
OS: Windows (All)
Status: NEW
Severity: normal
Pri
From: Marek Olšák
so that we can bind DCC (texture) as an image buffer.
---
src/gallium/drivers/radeonsi/si_descriptors.c | 9 ++---
src/gallium/drivers/radeonsi/si_pipe.h| 2 ++
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_descriptor
From: Marek Olšák
Needed by displayable DCC.
We need to flush L2 after rendering if PIPE_ALIGNED=0 and DCC is enabled.
---
src/gallium/drivers/radeonsi/si_blit.c| 7 ---
.../drivers/radeonsi/si_compute_blit.c| 9 +++--
src/gallium/drivers/radeonsi/si_pipe.h| 6
From: Marek Olšák
---
src/amd/common/ac_gpu_info.c | 8
src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.c | 4
2 files changed, 12 insertions(+)
diff --git a/src/amd/common/ac_gpu_info.c b/src/amd/common/ac_gpu_info.c
index d890172227c..c53335bbb7d 100644
---
From: Marek Olšák
This is the simpler codepath - just disable RB and pipe alignment for DCC.
---
src/amd/common/ac_gpu_info.c | 2 +
src/amd/common/ac_gpu_info.h | 3 +
src/amd/common/ac_surface.c| 25 +++-
src/amd/common/ac_surface.h
From: Marek Olšák
A compute shader is used to reorder DCC data from aligned to unaligned.
---
src/amd/common/ac_gpu_info.c | 1 +
src/amd/common/ac_gpu_info.h | 3 +
src/amd/common/ac_surface.c | 125 --
src/amd/common/ac_su
Hi,
This series enables DCC for scanout on Ravens.
It requires kernel driver version >= 3.31.0 and my xf86-video-amdgpu patch.
There is one issue to resolve: Steam crashes in addrlib/ComputeDccAddrFromCoord.
Please review,
Thanks,
Marek
___
mesa-dev
https://bugs.freedesktop.org/show_bug.cgi?id=109443
Jose Fonseca changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109535
Matt Turner changed:
What|Removed |Added
Depends on|109615 |
Referenced Bugs:
https://bugs.freedesk
https://bugs.freedesktop.org/show_bug.cgi?id=109615
Matt Turner changed:
What|Removed |Added
Blocks|109535 |
--- Comment #6 from Matt Turner ---
Let
https://bugs.freedesktop.org/show_bug.cgi?id=109443
--- Comment #10 from William Deegan ---
If you'd like to be notified when the fix gets merged into SCons please add
yourself to:
https://github.com/SCons/scons/pull/3311
Hopefully I'll get this wrapped up (need a test to cover this) and into m
On Thu, Feb 28, 2019 at 12:39 AM Boris Brezillon
wrote:
>
> Hello Gurchetan,
>
> On Wed, 27 Feb 2019 10:34:26 -0800
> Gurchetan Singh wrote:
>
> > On Mon, Feb 25, 2019 at 12:35 AM Boris Brezillon
> > wrote:
> > >
> > > From: Daniel Stone
> > >
> > > pipe_boxes are x/y + width/height, rather tha
On 2/28/19 4:47 AM, Iago Toral wrote:
> On Wed, 2019-02-27 at 17:04 -0800, Ian Romanick wrote:
>> On 2/27/19 4:45 AM, Iago Toral Quiroga wrote:
>>> Now that we propagate constants to the first source of 2src
>>> instructions we
>>> see more opportunities of constant folding in the backend.
>>>
>>>
This caused vmware driver build failure
Fixes: 6010d7b8e8 ("gallium: add PIPE_CAP_MAX_VARYINGS")
---
src/gallium/drivers/svga/svga_screen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/svga/svga_screen.c
b/src/gallium/drivers/svga/svga_screen.c
index 6c
https://bugs.freedesktop.org/show_bug.cgi?id=109805
Bug ID: 109805
Summary: GPU hangs with error
VM_CONTEXT1_PROTECTION_FAULT_STATUS
Product: Mesa
Version: 18.3
Hardware: x86-64 (AMD64)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=109805
--- Comment #1 from rainbowsforthe...@gmail.com
---
Created attachment 143504
--> https://bugs.freedesktop.org/attachment.cgi?id=143504&action=edit
glxinfo output
--
You are receiving this mail because:
You are the QA Contact for the bug.
Y
On 02/28/2019 08:00 PM, Neha Bhende wrote:
This caused vmware driver build failure
Fixes: 6010d7b8e8 ("gallium: add PIPE_CAP_MAX_VARYINGS")
---
src/gallium/drivers/svga/svga_screen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/svga/svga_screen.c
b/
Am 01.03.19 um 00:28 schrieb Gurchetan Singh:
> On Thu, Feb 28, 2019 at 12:39 AM Boris Brezillon
> wrote:
>>
>> Hello Gurchetan,
>>
>> On Wed, 27 Feb 2019 10:34:26 -0800
>> Gurchetan Singh wrote:
>>
>>> On Mon, Feb 25, 2019 at 12:35 AM Boris Brezillon
>>> wrote:
From: Daniel Stone
>>>
From: Mathias Fröhlich
Now that the buffer object usage history tracks if it is
being used as vertex buffer object, we can restrict setting
the ST_NEW_VERTEX_ARRAYS bit to dirty on glBufferData calls to
buffers that are potentially used as vertex buffer object.
Also put a note that the same could
From: Mathias Fröhlich
We already track the usage history for buffer objects
in a lot of aspects. Add GL_ARRAY_BUFFER and
GL_ELEMENT_ARRAY_BUFFER to gl_buffer_object::UsageHistory.
Signed-off-by: Mathias Fröhlich
---
src/mesa/main/arrayobj.c | 4 +++-
src/mesa/main/bufferobj.c | 5 +
src/
From: Mathias Fröhlich
Hi Brian,
I have an other VAO optimization aspect for review.
Currently gallium just invalidates the array state on every
glBufferData type call. The change adds buffer object
usage tracking for vertex buffer objects and avoids invalidating
array state on for example unifo
Dropping these makes the shaders more generic which can make it
better when using the serialized NIR as a key for in memory shader
caches such as what we do for radeonsi.
Also it just means we can write/read less to and from the disk cache.
---
src/compiler/nir/nir_serialize.c | 17 --
We know NIR can handle this because the shaders coming from spirv don't
have names. Dropping the name makes the shaders more generic which can
make it better when using the serialized NIR as a key for in memory
shader caches such as what we do for radeonsi.
Also it just means we can write/read les
We know NIR can handle this because the shaders coming from spirv don't
have names. Dropping the name makes the shaders more generic which can
make it better when using the serialized NIR as a key for in memory
shader caches such as what we do for radeonsi.
Also it just means we can write/read les
53 matches
Mail list logo
