Re: [PATCH v3 0/5] drm/v3d: Fix GPU stats inconsistencies and race-condition

2024-04-23 Thread Maíra Canal
On 4/23/24 04:05, Maxime Ripard wrote: Hi, On Mon, Apr 22, 2024 at 01:08:44PM -0300, Maíra Canal wrote: @drm-misc maintainers, is there any chance you could backport commit 35f4f8c9fc97 ("drm/v3d: Don't increment `enabled_ns` twice") [1] to drm- misc-next? I would like to apply this series to

Re: [PATCH v3 0/5] drm/v3d: Fix GPU stats inconsistencies and race-condition

2024-04-23 Thread Maxime Ripard
Hi, On Mon, Apr 22, 2024 at 01:08:44PM -0300, Maíra Canal wrote: > @drm-misc maintainers, is there any chance you could backport commit > 35f4f8c9fc97 ("drm/v3d: Don't increment `enabled_ns` twice") [1] to drm- > misc-next? > > I would like to apply this series to drm-misc-next because it fixes >

Re: [PATCH v3 0/5] drm/v3d: Fix GPU stats inconsistencies and race-condition

2024-04-22 Thread Maíra Canal
Hi, @drm-misc maintainers, is there any chance you could backport commit 35f4f8c9fc97 ("drm/v3d: Don't increment `enabled_ns` twice") [1] to drm- misc-next? I would like to apply this series to drm-misc-next because it fixes another issue with the GPU stats, but this series depends on commit 35f

[PATCH v3 0/5] drm/v3d: Fix GPU stats inconsistencies and race-condition

2024-04-20 Thread Maíra Canal
The first version of this series had the intention to fix two major issues with the GPU stats: 1. We were incrementing `enabled_ns` twice by the end of each job. 2. There is a race-condition between the IRQ handler and the users The first of the issues was already addressed and the fix was applie