dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
	"Abhinav Kumar" <abhinav.kumar@linux.dev>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Anna Maniscalco" <anna.maniscalco2000@gmail.com>,
	"Boris Brezillon" <boris.brezillon@collabora.com>,
	"David Airlie" <airlied@gmail.com>,
	"Dmitry Baryshkov" <lumag@kernel.org>,
	"Jessica Zhang" <jesszhan0024@gmail.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Liviu Dudau" <liviu.dudau@arm.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Marijn Suijten" <marijn.suijten@somainline.org>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Rob Clark" <robin.clark@oss.qualcomm.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Sean Paul" <sean@poorly.run>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Steven Price" <steven.price@arm.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH v2 0/5] drm/gpuvm: two pass locking for exec
Date: Thu, 1 Oct 2026 10:31:03 -0700	[thread overview]
Message-ID: <ar6Y1+fH0/w427ip@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <DLTOCUDLX5ZR.2DUZPGUB9CAE2@kernel.org>

On Thu, Oct 01, 2026 at 07:23:49PM +0200, Danilo Krummrich wrote:
> On Thu Oct 1, 2026 at 7:17 PM CEST, Matthew Brost wrote:
> > On Thu, Oct 01, 2026 at 06:43:13PM +0200, Danilo Krummrich wrote:
> >> On Thu Oct 1, 2026 at 6:19 PM CEST, Matthew Brost wrote:
> >> >   drm/msm: use DRM_GPUVM_RESV_PROTECTED for VM_BIND VMs
> >> 
> >> That's great! But the title suggests there are other VMs without this?
> >> 
> >
> > What exactly are you asking?
> 
> In my feedback from v1 I mentioned that having the feature for
> DRM_GPUVM_RESV_PROTECTED only is unfortunate and that I think that we could get
> rid of !DRM_GPUVM_RESV_PROTECTED entirely.
> 

Ah, okay, I clearly missed that. I use Patchwork to scan for feedback
because my inbox is a zoo, and for some reason this didn't show up in
Xe's Patchwork instance.

I see that you sent me a link, so let me take a look and reply. It was
obviously never my intent to ignore feedback.

> MSM and nouveau are the only users of !DRM_GPUVM_RESV_PROTECTED, and I mentioned
> in v1 that I'm happy to have a look at this after LPC. I.e. scanning the patch
> titles of v2 only, this looked like it was referring to this.

I'll be LPC too, so perhaps if we need to bottom out on anything there
we can discuss. Merging isn't pressing, as this won't make 7.4 window
anyways.

Matt

  reply	other threads:[~2026-10-01 17:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 16:19 [PATCH v2 0/5] drm/gpuvm: two pass locking for exec Matthew Brost
2026-10-01 16:19 ` [PATCH v2 1/5] drm/gpuvm: allow locking external objects in two passes Matthew Brost
2026-10-01 16:19 ` [PATCH v2 2/5] drm/xe: lock the resident BOs of an exec last Matthew Brost
2026-10-01 16:19 ` [PATCH v2 3/5] drm/panthor: lock the resident BOs of a submit last Matthew Brost
2026-10-01 16:20 ` [PATCH v2 4/5] drm/msm: use DRM_GPUVM_RESV_PROTECTED for VM_BIND VMs Matthew Brost
2026-10-01 16:43   ` sashiko-bot
2026-10-01 16:20 ` [PATCH v2 5/5] drm/msm: lock the resident BOs of a VM_BIND submit last Matthew Brost
2026-10-01 16:43 ` [PATCH v2 0/5] drm/gpuvm: two pass locking for exec Danilo Krummrich
2026-10-01 17:13   ` Danilo Krummrich
2026-10-01 17:23     ` Matthew Brost
2026-10-01 17:25       ` Danilo Krummrich
2026-10-01 17:17   ` Matthew Brost
2026-10-01 17:23     ` Danilo Krummrich
2026-10-01 17:31       ` Matthew Brost [this message]
2026-10-01 17:34         ` 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=ar6Y1+fH0/w427ip@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=abhinav.kumar@linux.dev \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=anna.maniscalco2000@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=corbet@lwn.net \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jesszhan0024@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=lumag@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marijn.suijten@somainline.org \
    --cc=mripard@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    --cc=skhan@linuxfoundation.org \
    --cc=steven.price@arm.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tzimmermann@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox