All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: "Danilo Krummrich" <dakr@redhat.com>,
	airlied@gmail.com, daniel@ffwll.ch, tzimmermann@suse.de,
	corbet@lwn.net, christian.koenig@amd.com, bskeggs@redhat.com,
	Liam.Howlett@oracle.com, matthew.brost@intel.com,
	alexdeucher@gmail.com, ogabbay@kernel.org, bagasdotme@gmail.com,
	willy@infradead.org, jason@jlekstrand.net,
	donald.robson@imgtec.com, dri-devel@lists.freedesktop.org,
	nouveau@lists.freedesktop.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Dave Airlie" <airlied@redhat.com>
Subject: Re: [PATCH drm-misc-next v8 01/12] drm: manager to keep track of GPUs VA mappings
Date: Fri, 28 Jul 2023 14:26:12 +0200	[thread overview]
Message-ID: <20230728142612.2ecf99ef@collabora.com> (raw)
In-Reply-To: <hi5magp4icayy5dxmylfyxws52cu63jvlhu4yj5xem3acoaylk@msf7zthcr3lg>

On Fri, 28 Jul 2023 13:31:36 +0200
Maxime Ripard <mripard@kernel.org> wrote:

> Hi Danilo,
> 
> On Thu, Jul 20, 2023 at 02:14:22AM +0200, Danilo Krummrich wrote:
> > Add infrastructure to keep track of GPU virtual address (VA) mappings
> > with a decicated VA space manager implementation.
> > 
> > New UAPIs, motivated by Vulkan sparse memory bindings graphics drivers
> > start implementing, allow userspace applications to request multiple and
> > arbitrary GPU VA mappings of buffer objects. The DRM GPU VA manager is
> > intended to serve the following purposes in this context.
> > 
> > 1) Provide infrastructure to track GPU VA allocations and mappings,
> >    making using an interval tree (RB-tree).
> > 
> > 2) Generically connect GPU VA mappings to their backing buffers, in
> >    particular DRM GEM objects.
> > 
> > 3) Provide a common implementation to perform more complex mapping
> >    operations on the GPU VA space. In particular splitting and merging
> >    of GPU VA mappings, e.g. for intersecting mapping requests or partial
> >    unmap requests.
> > 
> > Acked-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > Acked-by: Matthew Brost <matthew.brost@intel.com>
> > Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> > Tested-by: Matthew Brost <matthew.brost@intel.com>
> > Tested-by: Donald Robson <donald.robson@imgtec.com>
> > Suggested-by: Dave Airlie <airlied@redhat.com>
> > Signed-off-by: Danilo Krummrich <dakr@redhat.com>  
> 
> For some reason this breaks the drm_exec kunit patches:

Fix available here [1].

[1]https://lore.kernel.org/dri-devel/cbf4ccf9-8131-27a0-332c-6942866340d1@igalia.com/T/#t

WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: matthew.brost@intel.com,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	willy@infradead.org, dri-devel@lists.freedesktop.org,
	corbet@lwn.net, nouveau@lists.freedesktop.org,
	ogabbay@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Liam.Howlett@oracle.com,
	"Danilo Krummrich" <dakr@redhat.com>,
	bskeggs@redhat.com, tzimmermann@suse.de,
	"Dave Airlie" <airlied@redhat.com>,
	bagasdotme@gmail.com, christian.koenig@amd.com,
	jason@jlekstrand.net, donald.robson@imgtec.com
Subject: Re: [PATCH drm-misc-next v8 01/12] drm: manager to keep track of GPUs VA mappings
Date: Fri, 28 Jul 2023 14:26:12 +0200	[thread overview]
Message-ID: <20230728142612.2ecf99ef@collabora.com> (raw)
In-Reply-To: <hi5magp4icayy5dxmylfyxws52cu63jvlhu4yj5xem3acoaylk@msf7zthcr3lg>

On Fri, 28 Jul 2023 13:31:36 +0200
Maxime Ripard <mripard@kernel.org> wrote:

> Hi Danilo,
> 
> On Thu, Jul 20, 2023 at 02:14:22AM +0200, Danilo Krummrich wrote:
> > Add infrastructure to keep track of GPU virtual address (VA) mappings
> > with a decicated VA space manager implementation.
> > 
> > New UAPIs, motivated by Vulkan sparse memory bindings graphics drivers
> > start implementing, allow userspace applications to request multiple and
> > arbitrary GPU VA mappings of buffer objects. The DRM GPU VA manager is
> > intended to serve the following purposes in this context.
> > 
> > 1) Provide infrastructure to track GPU VA allocations and mappings,
> >    making using an interval tree (RB-tree).
> > 
> > 2) Generically connect GPU VA mappings to their backing buffers, in
> >    particular DRM GEM objects.
> > 
> > 3) Provide a common implementation to perform more complex mapping
> >    operations on the GPU VA space. In particular splitting and merging
> >    of GPU VA mappings, e.g. for intersecting mapping requests or partial
> >    unmap requests.
> > 
> > Acked-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > Acked-by: Matthew Brost <matthew.brost@intel.com>
> > Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> > Tested-by: Matthew Brost <matthew.brost@intel.com>
> > Tested-by: Donald Robson <donald.robson@imgtec.com>
> > Suggested-by: Dave Airlie <airlied@redhat.com>
> > Signed-off-by: Danilo Krummrich <dakr@redhat.com>  
> 
> For some reason this breaks the drm_exec kunit patches:

Fix available here [1].

[1]https://lore.kernel.org/dri-devel/cbf4ccf9-8131-27a0-332c-6942866340d1@igalia.com/T/#t

  reply	other threads:[~2023-07-28 12:27 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20  0:14 [PATCH drm-misc-next v8 00/12] DRM GPUVA Manager & Nouveau VM_BIND UAPI Danilo Krummrich
2023-07-20  0:14 ` Danilo Krummrich
2023-07-20  0:14 ` [Nouveau] " Danilo Krummrich
2023-07-20  0:14 ` [PATCH drm-misc-next v8 01/12] drm: manager to keep track of GPUs VA mappings Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20 10:44   ` Steven Price
2023-07-20 10:44     ` [Nouveau] " Steven Price
2023-07-20 21:48     ` Danilo Krummrich
2023-07-20 21:48       ` Danilo Krummrich
2023-07-20 21:48       ` [Nouveau] " Danilo Krummrich
2023-07-28 11:31   ` Maxime Ripard
2023-07-28 11:31     ` Maxime Ripard
2023-07-28 11:31     ` [Nouveau] " Maxime Ripard
2023-07-28 12:26     ` Boris Brezillon [this message]
2023-07-28 12:26       ` Boris Brezillon
2023-07-31 12:04       ` Maxime Ripard
2023-07-31 12:04         ` Maxime Ripard
2023-07-31 12:04         ` [Nouveau] " Maxime Ripard
2023-07-20  0:14 ` [PATCH drm-misc-next v8 02/12] drm: debugfs: provide infrastructure to dump a DRM GPU VA space Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20 10:51   ` Steven Price
2023-07-20 10:51     ` [Nouveau] " Steven Price
2023-07-20  0:14 ` [PATCH drm-misc-next v8 03/12] drm/nouveau: new VM_BIND uapi interfaces Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-21 22:58   ` Faith Ekstrand
2023-07-21 22:58     ` Faith Ekstrand
2023-07-25  2:03     ` Danilo Krummrich
2023-07-25  2:03       ` Danilo Krummrich
2023-07-25  2:03       ` [Nouveau] " Danilo Krummrich
2023-07-25 15:42       ` Faith Ekstrand
2023-07-25 15:42         ` Faith Ekstrand
2023-07-20  0:14 ` [PATCH drm-misc-next v8 04/12] drm/nouveau: get vmm via nouveau_cli_vmm() Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20  0:14 ` [PATCH drm-misc-next v8 05/12] drm/nouveau: bo: initialize GEM GPU VA interface Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20  0:14 ` [PATCH drm-misc-next v8 06/12] drm/nouveau: move usercopy helpers to nouveau_drv.h Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20  0:14 ` [PATCH drm-misc-next v8 07/12] drm/nouveau: fence: separate fence alloc and emit Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20  0:14 ` [PATCH drm-misc-next v8 08/12] drm/nouveau: fence: fail to emit when fence context is killed Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20  0:14 ` [PATCH drm-misc-next v8 09/12] drm/nouveau: chan: provide nouveau_channel_kill() Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20  0:14 ` [PATCH drm-misc-next v8 10/12] drm/nouveau: nvkm/vmm: implement raw ops to manage uvmm Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich
2023-07-20  0:14 ` [Nouveau] [PATCH drm-misc-next v8 11/12] drm/nouveau: implement new VM_BIND uAPI Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-22 15:12   ` [Nouveau] " Faith Ekstrand
2023-07-22 15:12     ` Faith Ekstrand
2023-07-23 23:54     ` Dave Airlie
2023-07-23 23:54       ` Dave Airlie
2023-07-23 23:54       ` [Nouveau] " Dave Airlie
2023-07-25  2:04     ` Danilo Krummrich
2023-07-25  2:04       ` Danilo Krummrich
2023-07-25  2:04       ` [Nouveau] " Danilo Krummrich
2023-07-25 16:16       ` Faith Ekstrand
2023-07-25 16:16         ` Faith Ekstrand
2023-07-25 16:43         ` Danilo Krummrich
2023-07-25 16:43           ` Danilo Krummrich
2023-07-25 16:43           ` [Nouveau] " Danilo Krummrich
2023-07-25 21:00           ` Danilo Krummrich
2023-07-25 21:00             ` Danilo Krummrich
2023-07-25 21:00             ` [Nouveau] " Danilo Krummrich
2023-07-31  3:30             ` Faith Ekstrand
2023-07-31  3:30               ` Faith Ekstrand
2023-07-31 16:39               ` [Nouveau] " Faith Ekstrand
2023-07-31 16:39                 ` Faith Ekstrand
2023-07-20  0:14 ` [PATCH drm-misc-next v8 12/12] drm/nouveau: debugfs: implement DRM GPU VA debugfs Danilo Krummrich
2023-07-20  0:14   ` Danilo Krummrich
2023-07-20  0:14   ` [Nouveau] " Danilo Krummrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230728142612.2ecf99ef@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=alexdeucher@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=bskeggs@redhat.com \
    --cc=christian.koenig@amd.com \
    --cc=corbet@lwn.net \
    --cc=dakr@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=donald.robson@imgtec.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jason@jlekstrand.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=mripard@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ogabbay@kernel.org \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tzimmermann@suse.de \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.