mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jayden Milne <me@jayd.ml>
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
	"Rob Clark" <robin.clark@oss.qualcomm.com>,
	"Dmitry Baryshkov" <lumag@kernel.org>,
	"Abhinav Kumar" <abhinav.kumar@linux.dev>,
	"Jessica Zhang" <jesszhan0024@gmail.com>,
	"Sean Paul" <sean@poorly.run>,
	"Marijn Suijten" <marijn.suijten@somainline.org>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Konrad Dybcio" <konradybcio@kernel.org>,
	"Akhil P Oommen" <akhilpo@oss.qualcomm.com>,
	"Sumit Semwal" <sumit.semwal@linaro.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Antonino Maniscalco" <antomani103@gmail.com>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH 0/2] drm/msm: fix dma-buf sharing on targets without per-process pgtables
Date: Mon, 2 Nov 2026 20:02:26 -0700	[thread overview]
Message-ID: <ee4b739d-6cec-431f-94e0-b551c359cd96@jayd.ml> (raw)
In-Reply-To: <20260822-msm-fix-export-v1-0-917b3cbedd43@oss.qualcomm.com>

On Sat, Aug 22, 2026 at 11:48:57AM +0300, Dmitry Baryshkov wrote:
> Targets without per-process pgtables -- everything pre-a6xx, plus
> a6xx parts where split pagetables are unavailable -- hand every DRM
> file the GPU's global VM.  The rest of the driver still treats a
> context VM as private to that context, so closing a handle tears down
> mappings other files are still using, and frees the iova for
> immediate reuse.

I tested this series on a530 (Samsung Galaxy Tab S3, APQ8096) on v7.3.1
and v6.19.5 (with some backporting).

When I was bringing up v6.19.5 KWin would reliably trigger TRANSLATION
read faults when rotating the screen with the lock screen up - 1800
observed over 8 rotations. After the series the same test gave no faults
on v6.19.5 or v7.3.1.

I didn't re-test v7.3.1 without the series - if that would help, I can
set it up.

Tested-by: Jayden Milne <linux@jayd.ml> # a530

      parent reply	other threads:[~2026-11-03  3:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22  8:48 Dmitry Baryshkov
2026-08-22  8:48 ` [PATCH 1/2] drm/msm: factor out a locking put_iova_spaces() wrapper Dmitry Baryshkov
2026-08-22  8:48 ` [PATCH 2/2] drm/msm: don't tear down shared VM mappings on handle close Dmitry Baryshkov
2026-10-05 14:54   ` Rob Clark
2026-10-27 11:06     ` Dmitry Baryshkov
2026-10-09  2:16   ` Alexey Minnekhanov
2026-11-03  3:02 ` Jayden Milne [this message]

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=ee4b739d-6cec-431f-94e0-b551c359cd96@jayd.ml \
    --to=me@jayd.ml \
    --cc=abhinav.kumar@linux.dev \
    --cc=airlied@gmail.com \
    --cc=akhilpo@oss.qualcomm.com \
    --cc=antomani103@gmail.com \
    --cc=christian.koenig@amd.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jesszhan0024@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    --cc=sumit.semwal@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®