From: Vivek Kasireddy <vivek.kasireddy@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
tvrtko.ursulin@linux.intel.com
Subject: [Intel-gfx] [PATCH v6 0/2] drm/mm: Add an iterator to optimally walk over holes suitable for an allocation
Date: Mon, 7 Mar 2022 12:21:19 -0800 [thread overview]
Message-ID: <20220307202121.389550-1-vivek.kasireddy@intel.com> (raw)
The first patch is a drm core patch that replaces the for loop in
drm_mm_insert_node_in_range() with the iterator and would not
cause any functional changes. The second patch is a i915 driver
specific patch that also uses the iterator but solves a different
problem.
v2:
- Added a new patch to this series to fix a potential NULL
dereference.
- Fixed a typo associated with the iterator introduced in the
drm core patch.
- Added locking around the snippet in the i915 patch that
traverses the GGTT hole nodes.
v3: (Tvrtko)
- Replaced mutex_lock with mutex_lock_interruptible_nested() in
the i915 patch.
v4: (Tvrtko)
- Dropped the patch added in v2 as it was deemed unnecessary.
v5: (Tvrtko)
- Fixed yet another typo in the drm core patch: should have
passed caller_mode instead of mode to the iterator.
v6: (Tvrtko)
- Fixed the checkpatch warning that warns about precedence issues.
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Nirmoy Das <nirmoy.das@intel.com>
Cc: Christian König <christian.koenig@amd.com>
Vivek Kasireddy (2):
drm/mm: Add an iterator to optimally walk over holes for an allocation
(v6)
drm/i915/gem: Don't try to map and fence large scanout buffers (v9)
drivers/gpu/drm/drm_mm.c | 32 ++++----
drivers/gpu/drm/i915/i915_gem.c | 128 +++++++++++++++++++++++---------
include/drm/drm_mm.h | 36 +++++++++
3 files changed, 145 insertions(+), 51 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-07 20:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 20:21 Vivek Kasireddy [this message]
2022-03-07 20:21 ` [Intel-gfx] [PATCH v6 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v6) Vivek Kasireddy
2022-03-07 20:21 ` [Intel-gfx] [PATCH v6 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v9) Vivek Kasireddy
2022-03-11 9:39 ` Daniel Vetter
2022-03-14 11:14 ` Tvrtko Ursulin
2022-03-15 7:28 ` Kasireddy, Vivek
2022-03-15 9:45 ` Tvrtko Ursulin
2022-03-16 7:37 ` Kasireddy, Vivek
2022-03-16 13:34 ` Tvrtko Ursulin
2022-03-17 7:08 ` Kasireddy, Vivek
2022-03-17 10:33 ` Tvrtko Ursulin
2022-03-17 9:47 ` Daniel Vetter
2022-03-17 10:04 ` Tvrtko Ursulin
2022-03-17 10:10 ` Daniel Vetter
2022-03-07 20:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/mm: Add an iterator to optimally walk over holes suitable for an allocation Patchwork
2022-03-07 20:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-08 12:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-09 18:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/mm: Add an iterator to optimally walk over holes suitable for an allocation (rev2) Patchwork
2022-03-09 18:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-09 19:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-10 5:00 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=20220307202121.389550-1-vivek.kasireddy@intel.com \
--to=vivek.kasireddy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.com \
/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