All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, etnaviv@lists.freedesktop.org,
	 kernel@pengutronix.de
Subject: [GIT PULL] etnaviv-fixes for 5.15
Date: Thu, 16 Sep 2021 13:54:03 +0200	[thread overview]
Message-ID: <729a561b6cfed090457bcc856a9e14ed6209fe21.camel@pengutronix.de> (raw)

Hi Dave, Daniel,

please pull those etnaviv changes as fixes for the 5.15 release
series. 

Fixes a very annoying issue where the driver view of the MMU state gets
out of sync with the actual hardware state across a runtime PM cycle,
so we end up restarting the GPU with the wrong (potentially already
freed) MMU context. Hilarity ensues.

Regards,
Lucas

The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:

  Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)

are available in the Git repository at:

  https://git.pengutronix.de/git/lst/linux etnaviv/fixes

for you to fetch changes up to f2faea8b64125852fa9acc6771c07fc0311a039b:

  drm/etnaviv: add missing MMU context put when reaping MMU mapping (2021-09-16 10:35:37 +0200)

----------------------------------------------------------------
Lucas Stach (8):
      drm/etnaviv: return context from etnaviv_iommu_context_get
      drm/etnaviv: put submit prev MMU context when it exists
      drm/etnaviv: stop abusing mmu_context as FE running marker
      drm/etnaviv: keep MMU context across runtime suspend/resume
      drm/etnaviv: exec and MMU state is lost when resetting the GPU
      drm/etnaviv: fix MMU context leak on GPU reset
      drm/etnaviv: reference MMU context when setting up hardware state
      drm/etnaviv: add missing MMU context put when reaping MMU mapping

 drivers/gpu/drm/etnaviv/etnaviv_buffer.c     |  3 +--
 drivers/gpu/drm/etnaviv/etnaviv_gem.c        |  3 +--
 drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c |  3 +--
 drivers/gpu/drm/etnaviv/etnaviv_gpu.c        | 43 +++++++++++++++++++++++++------------------
 drivers/gpu/drm/etnaviv/etnaviv_gpu.h        |  1 +
 drivers/gpu/drm/etnaviv/etnaviv_iommu.c      |  4 ++++
 drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c   |  8 ++++++++
 drivers/gpu/drm/etnaviv/etnaviv_mmu.c        |  1 +
 drivers/gpu/drm/etnaviv/etnaviv_mmu.h        |  4 +++-
 9 files changed, 45 insertions(+), 25 deletions(-)



                 reply	other threads:[~2021-09-16 11:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=729a561b6cfed090457bcc856a9e14ed6209fe21.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=kernel@pengutronix.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 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.