On Thu, Jul 20, 2023 at 3:55 AM Tvrtko Ursulin
wrote:
>
>
> Hi,
>
> On 19/07/2023 21:31, T.J. Mercier wrote:
> > On Wed, Jul 12, 2023 at 4:47 AM Tvrtko Ursulin
> > wrote:
> >>
> >>drm.memory.stat
> >> A nested file conta
On Wed, Jul 12, 2023 at 4:47 AM Tvrtko Ursulin
wrote:
>
> drm.memory.stat
> A nested file containing cumulative memory statistics for the whole
> sub-hierarchy, broken down into separate GPUs and separate memory
> regions supported by the latter.
>
> For
On Wed, Jun 21, 2023 at 11:16 AM Dmitry Osipenko
wrote:
>
> Hi,
>
> On 6/21/23 20:21, T.J. Mercier wrote:
> > On Mon, May 29, 2023 at 3:46 PM Dmitry Osipenko
> > wrote:
> >>
> >> Don't assert held dma-buf reservation lock on memory mapping of exported
&g
On Mon, May 29, 2023 at 3:46 PM Dmitry Osipenko
wrote:
>
> Don't assert held dma-buf reservation lock on memory mapping of exported
> buffer.
>
> We're going to change dma-buf mmap() locking policy such that exporters
> will have to handle the lock. The previous locking policy caused deadlock
>
On Wed, Oct 19, 2022 at 10:34 AM Tvrtko Ursulin
wrote:
>
> From: Tvrtko Ursulin
>
> Add a scanning worker, which if enabled, periodically queries the cgroup
> for GPU usage and if over budget (as configured by it's relative weight
> share) notifies the drm core about the fact.
>
> This is off by
