Hi,
Just for you to know. I opened an issue on Mesa's gitalb too about the
regression https://gitlab.freedesktop.org/mesa/mesa/-/issues/11105.
Thanks for the help.
Regards,
João Paulo Gonçalves
Hi Daniel,
On Fri, Apr 26, 2024 at 12:17:33PM +0100, Daniel Stone wrote:
> One thing you can try is to edit
> weston/libweston/backend-drm/state-propose.c and, inside
> dmabuf_feedback_maybe_update(), prevent action_needed from ever being
> set to ACTION_NEEDED_ADD_SCANOUT_TRANCHE. It would be
Hi Joao,
On Fri, 26 Apr 2024 at 08:42, Joao Paulo Silva Goncalves
wrote:
> On Thu, Apr 25, 2024 at 9:08 AM Lucas Stach wrote:
> > I can reproduce the issue, but sadly there is no simple fix for this,
> > as it's a bad interaction between some of the new features.
> > At the core of the issue is
On Thu, Apr 25, 2024 at 9:08 AM Lucas Stach wrote:
> I can reproduce the issue, but sadly there is no simple fix for this,
> as it's a bad interaction between some of the new features.
> At the core of the issue is the dmabuf-feedback support with the chain
> of events being as follows:
> 1.
On Thu, Apr 25, 2024 at 5:58 AM Lucas Stach wrote:
> Etnaviv added some resource tracking to fix issues with a number of
> use-cases, which did add some CPU overhead and might cost some
> performance, but should no be as dramatic as the numbers you are seeing
> here.
Good to know. Thanks!
>
On Thu, 25 Apr 2024 at 13:08, Lucas Stach wrote:
> I can reproduce the issue, but sadly there is no simple fix for this,
> as it's a bad interaction between some of the new features.
> At the core of the issue is the dmabuf-feedback support with the chain
> of events being as follows:
>
> 1.
Am Donnerstag, dem 25.04.2024 um 07:56 -0300 schrieb Joao Paulo Silva
Goncalves:
>
>
> On Thu, Apr 25, 2024 at 5:58 AM Lucas Stach wrote:
>
> > Etnaviv added some resource tracking to fix issues with a number of
> > use-cases, which did add some CPU overhead and might cost some
> >
Hi Joao Paulo,
Am Mittwoch, dem 24.04.2024 um 19:31 -0300 schrieb Joao Paulo Silva
Goncalves:
> Hello all,
>
> We might have encountered a performance regression after upgrading from Mesa
> 2022.0.3 to 2024.0.2. During our automated hardware tests using LAVA, we
> noticed
> a lower score on
Hello all,
We might have encountered a performance regression after upgrading from Mesa
2022.0.3 to 2024.0.2. During our automated hardware tests using LAVA, we noticed
a lower score on glmark2 when we upgraded from the OpenEmbedded release from
Kirkstone to Scartgarth. After conducting some
