From: Vivek Kasireddy <vivek.kasireddy@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: "Christian König" <christian.koenig@amd.com>,
"Nirmoy Das" <nirmoy.das@intel.com>
Subject: [Intel-gfx] [PATCH v2 0/3] drm/mm: Add an iterator to optimally walk over holes suitable for an allocation
Date: Wed, 16 Feb 2022 23:50:11 -0800 [thread overview]
Message-ID: <20220217075014.922605-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.
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 (3):
drm/mm: Ensure that the entry is not NULL before extracting rb_node
drm/mm: Add an iterator to optimally walk over holes for an allocation
(v4)
drm/i915/gem: Don't try to map and fence large scanout buffers (v8)
drivers/gpu/drm/drm_mm.c | 37 +++++-----
drivers/gpu/drm/i915/i915_gem.c | 124 +++++++++++++++++++++++---------
include/drm/drm_mm.h | 36 ++++++++++
3 files changed, 144 insertions(+), 53 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-17 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 7:50 Vivek Kasireddy [this message]
2022-02-17 7:50 ` [Intel-gfx] [PATCH v2 1/3] drm/mm: Ensure that the entry is not NULL before extracting rb_node Vivek Kasireddy
2022-02-17 9:09 ` Tvrtko Ursulin
2022-02-18 3:47 ` Kasireddy, Vivek
2022-02-21 12:39 ` Tvrtko Ursulin
2022-02-23 4:35 ` Kasireddy, Vivek
2022-02-23 14:03 ` Tvrtko Ursulin
2022-02-17 7:50 ` [Intel-gfx] [PATCH v2 2/3] drm/mm: Add an iterator to optimally walk over holes for an allocation (v4) Vivek Kasireddy
2022-02-17 7:50 ` [Intel-gfx] [PATCH v2 3/3] drm/i915/gem: Don't try to map and fence large scanout buffers (v8) Vivek Kasireddy
2022-02-17 9:19 ` Tvrtko Ursulin
2022-02-17 18:48 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/mm: Add an iterator to optimally walk over holes suitable for an allocation (rev2) Patchwork
2022-02-17 18:51 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-17 19:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-18 5:14 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20220217075014.922605-1-vivek.kasireddy@intel.com \
--to=vivek.kasireddy@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@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