[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230922134548.7ede67c0@collabora.com>
Date: Fri, 22 Sep 2023 13:45:48 +0200
From: Boris Brezillon <boris.brezillon@...labora.com>
To: Danilo Krummrich <dakr@...hat.com>
Cc: airlied@...il.com, daniel@...ll.ch, matthew.brost@...el.com,
thomas.hellstrom@...ux.intel.com, sarah.walker@...tec.com,
donald.robson@...tec.com, christian.koenig@....com,
faith.ekstrand@...labora.com, dri-devel@...ts.freedesktop.org,
nouveau@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH drm-misc-next v4 7/8] drm/gpuvm: generalize
dma_resv/extobj handling and GEM validation
On Wed, 20 Sep 2023 16:42:40 +0200
Danilo Krummrich <dakr@...hat.com> wrote:
> + /**
> + * @DRM_GPUVM_RESV_PROTECTED: GPUVM is protected externally by the
> + * GPUVM's &dma_resv lock
I think we need to be more specific, and list the fields/operations
that need to be externally protected when DRM_GPUVM_RESV_PROTECTED is
set.
> + */
> + DRM_GPUVM_RESV_PROTECTED = (1 << 0),
Powered by blists - more mailing lists