https://bugs.freedesktop.org/show_bug.cgi?id=111510
--- Comment #4 from Dieter Nützel ---
Maybe duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=111523 ?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=111510
LoneVVolf changed:
What|Removed |Added
Component|Gallium/StateTracker/galliu |Gallium/StateTracker/Clover
https://bugs.freedesktop.org/show_bug.cgi?id=111510
--- Comment #3 from LoneVVolf ---
You're right, Axel.
I didn't have logs of the fail, so did a fresh build (log attached).
The problem is not with gallium-nine, but with clover / opencl .
When building with gallium-opencl=disabled build finish
https://bugs.freedesktop.org/show_bug.cgi?id=111510
--- Comment #2 from LoneVVolf ---
Created attachment 145221
--> https://bugs.freedesktop.org/attachment.cgi?id=145221&action=edit
build log
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for
Just adding to the pile of :+1:
I think an empty repo for drm with just issues enabled is a good solution.
On Thursday, 2019-08-29 11:52:51 -0700, Kenneth Graunke wrote:
> Hi all,
>
> As a lot of you have probably noticed, Bugzilla seems to be getting a
> lot of spam these days - several of us h
https://bugs.freedesktop.org/show_bug.cgi?id=111493
Ian Romanick changed:
What|Removed |Added
Keywords||bisected, regression
--
You are receivi
https://bugs.freedesktop.org/show_bug.cgi?id=111493
--- Comment #4 from Ian Romanick ---
This is almost certainly a dup of
https://bugs.freedesktop.org/show_bug.cgi?id=111490, but I'm going to wait a
bit to close it as such.
--
You are receiving this mail because:
You are the QA Contact for the
https://bugs.freedesktop.org/show_bug.cgi?id=111493
Ian Romanick changed:
What|Removed |Added
Blocks||111444
Assignee|mesa-dev@lists
https://bugs.freedesktop.org/show_bug.cgi?id=111444
Ian Romanick changed:
What|Removed |Added
Depends on||111493
Referenced Bugs:
https://bugs.f
https://bugs.freedesktop.org/show_bug.cgi?id=111308
Ian Romanick changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
On Fri, 30 Aug 2019 10:35:57 -0700
Alyssa Rosenzweig wrote:
> > +struct panfrost_job_batch *batch =
> > panfrost_job_get_batch_for_fbo(ctx);
>
> This is verbose. Could we do across this patch:
>
> s/panfrost_job_batch/panfrost_batch/g
> s/panfrost_job_get_batch_for_fbo/panfrost_get_b
This series is R-b, provided Boris's comments are addressed (although it
sounds like he'll address them himself and push)
Nice debuging :)
On Fri, Aug 30, 2019 at 06:00:12PM +0200, Rohan Garg wrote:
> Jobs _must_ only be shared across the same context, having
> the last_job tracked in a screen ca
Patch 1 is reviewed-by.
Patch 2 I commented on for a v2.
Patch 3 and 4 will be reviewed-by once they're updated with the patch 2
rename (merge conflicts).
On Fri, Aug 30, 2019 at 04:05:33PM +0200, Boris Brezillon wrote:
> Hello,
>
> I'm currently reworking the job flushing logic to allow and I
> +struct panfrost_job_batch *batch =
> panfrost_job_get_batch_for_fbo(ctx);
This is verbose. Could we do across this patch:
s/panfrost_job_batch/panfrost_batch/g
s/panfrost_job_get_batch_for_fbo/panfrost_get_batch_for_fbo/g
signature.asc
Description: PGP signature
On Fri, 30 Aug 2019 18:00:13 +0200
Rohan Garg wrote:
> Both the BO cache and the transient pool are shared across
> context's. Protect access to these with mutexes.
>
> Signed-off-by: Rohan Garg
> --- a/src/gallium/drivers/panfrost/pan_screen.c
> +++ b/src/gallium/drivers/panfrost/pan_screen.c
On Fri, 30 Aug 2019 18:00:12 +0200
Rohan Garg wrote:
> Jobs _must_ only be shared across the same context, having
> the last_job tracked in a screen causes use-after-free issues
> and memory corruptions.
>
> Signed-off-by: Rohan Garg
Reviewed-by: Boris Brezillon
> ---
> src/gallium/drivers/
On Fri, 30 Aug 2019 18:56:52 +0200
Michel Dänzer wrote:
> On 2019-08-30 6:52 p.m., Boris Brezillon wrote:
> > On Fri, 30 Aug 2019 18:43:59 +0200
> > Michel Dänzer wrote:
> >
> >>> diff --git a/include/GL/internal/dri_interface.h
> >>> b/include/GL/internal/dri_interface.h
> >>> index 4c60d34
On 2019-08-30 6:52 p.m., Boris Brezillon wrote:
> On Fri, 30 Aug 2019 18:43:59 +0200
> Michel Dänzer wrote:
>
>>> diff --git a/include/GL/internal/dri_interface.h
>>> b/include/GL/internal/dri_interface.h
>>> index 4c60d349ddd5..e04bed689219 100644
>>> --- a/include/GL/internal/dri_interface.h
>
On Fri, 30 Aug 2019 18:43:59 +0200
Michel Dänzer wrote:
> On 2019-08-29 1:54 p.m., Boris Brezillon wrote:
> > So we can call st_validate_state() from dri2_set_damage_region() in
> > order to update the BACK_LEFT attachement before using it. If we don't
> > do that, the resource passed to pipe_scr
Hello list,
The candidate for the Mesa 19.1.6 is now available. Currently we have:
- 17 queued
- 0 nominated (outstanding)
- and 3 rejected patch
The current queue consist as usual on fixes for different parts, but nothing
outstanding.
Take a look at section "Mesa stable queue" for more inf
On 2019-08-29 1:54 p.m., Boris Brezillon wrote:
> So we can call st_validate_state() from dri2_set_damage_region() in
> order to update the BACK_LEFT attachement before using it. If we don't
> do that, the resource passed to pipe_screen->set_damage_region() might
> be wrong.
>
> Signed-off-by: Bor
https://bugs.freedesktop.org/show_bug.cgi?id=111522
--- Comment #6 from MWATTT ---
Applying 1819 patch + /.drirc file doesn't have any effects.
--
You are receiving this mail because:
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev
Jobs _must_ only be shared across the same context, having
the last_job tracked in a screen causes use-after-free issues
and memory corruptions.
Signed-off-by: Rohan Garg
---
src/gallium/drivers/panfrost/pan_context.c | 10 +-
src/gallium/drivers/panfrost/pan_context.h | 6 ++
src/g
Both the BO cache and the transient pool are shared across
context's. Protect access to these with mutexes.
Signed-off-by: Rohan Garg
---
src/gallium/drivers/panfrost/pan_allocate.c | 2 ++
src/gallium/drivers/panfrost/pan_bo_cache.c | 16 +++-
src/gallium/drivers/panfrost/pan_job.c
https://bugs.freedesktop.org/show_bug.cgi?id=111444
Clayton Craft changed:
What|Removed |Added
Depends on||110507
Referenced Bugs:
https://bugs.
https://bugs.freedesktop.org/show_bug.cgi?id=111444
Clayton Craft changed:
What|Removed |Added
Depends on||110814
Referenced Bugs:
https://bugs.
https://bugs.freedesktop.org/show_bug.cgi?id=25
--- Comment #5 from zefkerri...@gmail.com ---
(In reply to Samuel Pitoiset from comment #4)
> Are you still able to reproduce the problem?
Yes, it's still here with the latest Mesa commit.
--
You are receiving this mail because:
You are the QA
Given the function name it makes more sense to pass it a job batch
directly.
Signed-off-by: Boris Brezillon
---
src/gallium/drivers/panfrost/pan_drm.c| 13 ++---
src/gallium/drivers/panfrost/pan_job.c| 2 +-
src/gallium/drivers/panfrost/pan_screen.h | 2 +-
3 files changed, 8 i
What we currently call a job is actually a batch containing several jobs
all attached to a rendering operation targeting a specific FBO.
Let's rename structs, functions, variables and fields to reflect this
fact.
Suggested-by: Alyssa Rosenzweig
Signed-off-by: Boris Brezillon
---
src/gallium/dr
Hello,
I'm currently reworking the job flushing logic to allow and I noticed
a few things in the existing that could be addressed independently.
Patch 1 is addressing a TODO, though the additional panfrost_job_add_bo()
is probably only needed for debug purpose (there's no risk of
use-after-free h
Memory allocated through panfrost_allocate_transient() is likely to
come from the transient pool. Let's add the BO backing the allocated
memory region to the job batch so the kernel can retain this BO while
jobs are executed.
In practice that has never been a problem because the transient pool
is
The context can be retrieved from batch->ctx.
Signed-off-by: Boris Brezillon
---
src/gallium/drivers/panfrost/pan_context.c | 6 +++---
src/gallium/drivers/panfrost/pan_drm.c | 2 +-
src/gallium/drivers/panfrost/pan_job.c | 24 ++
src/gallium/drivers/panfrost/pan_jo
Quoting Daniel Stone (2019-08-30 14:13:08)
> Hi,
>
> On Thu, 29 Aug 2019 at 21:35, Chris Wilson wrote:
> > Quoting Kristian Høgsberg (2019-08-29 21:20:12)
> > > On Thu, Aug 29, 2019 at 12:44 PM Chris Wilson
> > > wrote:
> > > > Quoting Kenneth Graunke (2019-08-29 19:52:51)
> > > > > - Moving bu
https://bugs.freedesktop.org/show_bug.cgi?id=111493
James B changed:
What|Removed |Added
CC||lejims...@gmail.com
--
You are receiving thi
Hi,
On Thu, 29 Aug 2019 at 21:35, Chris Wilson wrote:
> Quoting Kristian Høgsberg (2019-08-29 21:20:12)
> > On Thu, Aug 29, 2019 at 12:44 PM Chris Wilson
> > wrote:
> > > Quoting Kenneth Graunke (2019-08-29 19:52:51)
> > > > - Moving bug reports between the kernel and Mesa would be harder.
> >
https://bugs.freedesktop.org/show_bug.cgi?id=111522
--- Comment #5 from Eric Engestrom ---
Alright, you'll need to add this to your ~/.drirc on top of MR !1819:
If you could test other UE4 games too that would be great :)
--
You are receiving this ma
https://bugs.freedesktop.org/show_bug.cgi?id=111522
--- Comment #4 from MWATTT ---
The binary is "Supraland-Linux-Shipping"
It may also affect others UE4 games. Haven't tested yet
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=111522
Eero Tamminen changed:
What|Removed |Added
Blocks||111444
Referenced Bugs:
https://bugs.
https://bugs.freedesktop.org/show_bug.cgi?id=111444
Eero Tamminen changed:
What|Removed |Added
Depends on||111522
Referenced Bugs:
https://bugs.
https://bugs.freedesktop.org/show_bug.cgi?id=111522
--- Comment #3 from Eero Tamminen ---
(In reply to Eric Engestrom from comment #2)
> Could you try if this fixes your issue?
> https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1819
Not alone, as that MR enables the workaround only for gf
https://bugs.freedesktop.org/show_bug.cgi?id=111444
Denis changed:
What|Removed |Added
CC||denys.kos...@globallogic.co
|
https://bugs.freedesktop.org/show_bug.cgi?id=111522
Eric Engestrom changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #2 from Eric Enge
https://bugs.freedesktop.org/show_bug.cgi?id=106348
Mike Lothian changed:
What|Removed |Added
CC||m...@fireburn.co.uk
Resolution|-
On 2019-08-28 1:56 p.m., Jose Fonseca wrote:
> Hi Michel,
>
>> Good to see you guys starting to take better advantage of the
>> GitLab CI pipeline.
>
> Gitlab CI integration is complicated (very configurable), but I can
> tell from my experience with my own personal Github projects that
> having
On 30/8/19 0:52, apinheiro wrote:
On 7/8/19 10:44, Emil Velikov wrote:
Hi all,
Hi Emil,
On Wed, 31 Jul 2019 at 09:37, Emil Velikov
wrote:
Hi all,
Here is the tentative release plan for 19.2.0.
As many of you are well aware, it's time to the next branch point.
The calendar is alread
On 2019-08-29 9:36 p.m., Rob Clark wrote:
> On Thu, Aug 29, 2019 at 12:02 PM Kenneth Graunke
> wrote:
>>
>> - Moving bug reports between the kernel and Mesa would be harder.
>> We would have to open a bug in the other system. (Then again,
>> moving bugs between Mesa and X or Wayland would be
https://bugs.freedesktop.org/show_bug.cgi?id=111522
--- Comment #1 from Eero Tamminen ---
Related to bug 110765 ?
--
You are receiving this mail because:
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https:/
47 matches
Mail list logo
