From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "David Airlie" <airlied@linux.ie>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Chia-I Wu" <olvaffe@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Emil Velikov" <emil.l.velikov@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"Thomas Hellström" <thomas_os@shipmail.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Dmitry Osipenko <digetx@gmail.com>,
linux-tegra@vger.kernel.org, kernel@collabora.com,
virtualization@lists.linux-foundation.org
Subject: [PATCH v7 0/2] DRM GEM fixes
Date: Thu, 30 Jun 2022 23:04:03 +0300 [thread overview]
Message-ID: <20220630200405.1883897-1-dmitry.osipenko@collabora.com> (raw)
This patchset fixes two problems in the common GEM code. First fixed problem
is the bogus lockdep splat that complicates debugging of DRM drivers. Second
problem is the inconsistency in behaviour and improper handling of mapping
the imported GEMs by some drivers, to fix it we will prohibit to map the
imported GEMs like majority of drivers already do.
Changelog:
v7: - Factored out GEM patches from [1] since I'll be working on the
dma-buf locking in a separate patchsets now.
[1] https://lore.kernel.org/all/20220526235040.678984-1-dmitry.osipenko@collabora.com/
- Improved commit message and added fixes tag to the "Properly annotate
WW context" patch.
- Replaced "Move mapping of imported dma-bufs to drm_gem_mmap_obj()"
patch with "Don't map imported GEMs", like was suggested by
Thomas Hellström.
- Added r-b and suggested-by from Thomas Hellström.
Dmitry Osipenko (2):
drm/gem: Properly annotate WW context on drm_gem_lock_reservations()
error
drm/gem: Don't map imported GEMs
drivers/gpu/drm/drm_gem.c | 8 ++++++--
drivers/gpu/drm/drm_gem_shmem_helper.c | 9 ---------
2 files changed, 6 insertions(+), 11 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-30 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 20:04 Dmitry Osipenko [this message]
2022-06-30 20:04 ` [PATCH v7 1/2] drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error Dmitry Osipenko
2022-08-09 16:41 ` Daniel Vetter
2022-06-30 20:04 ` [PATCH v7 2/2] drm/gem: Don't map imported GEMs Dmitry Osipenko
2022-06-30 20:15 ` Thomas Hellström (Intel)
2022-06-30 20:22 ` Dmitry Osipenko
2022-06-30 20:26 ` Thomas Hellström (Intel)
2022-07-01 8:22 ` Dmitry Osipenko
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=20220630200405.1883897-1-dmitry.osipenko@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=gurchetansingh@chromium.org \
--cc=kernel@collabora.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=thomas_os@shipmail.org \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.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