From: Nirmoy Das <nirmoy.das@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>, Matthew Auld <matthew.auld@intel.com>
Subject: [PATCH] drm/i915: Use enum mode in drm_mm_insert_node_in_range
Date: Tue, 9 Apr 2024 13:15:41 +0200 [thread overview]
Message-ID: <20240409111541.2478-1-nirmoy.das@intel.com> (raw)
Use DRM_MM_INSERT_BEST as mode instead of zero.
Cc: Matthew Auld <matthew.auld@intel.com>
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
---
drivers/gpu/drm/xe/xe_ggtt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_ggtt.c b/drivers/gpu/drm/xe/xe_ggtt.c
index ff2239c0eda5..910153eed457 100644
--- a/drivers/gpu/drm/xe/xe_ggtt.c
+++ b/drivers/gpu/drm/xe/xe_ggtt.c
@@ -408,7 +408,8 @@ static int __xe_ggtt_insert_bo_at(struct xe_ggtt *ggtt, struct xe_bo *bo,
xe_device_mem_access_get(tile_to_xe(ggtt->tile));
mutex_lock(&ggtt->lock);
err = drm_mm_insert_node_in_range(&ggtt->mm, &bo->ggtt_node, bo->size,
- alignment, 0, start, end, 0);
+ alignment, 0, start, end,
+ DRM_MM_INSERT_BEST);
if (!err)
xe_ggtt_map_bo(ggtt, bo);
mutex_unlock(&ggtt->lock);
--
2.42.0
next reply other threads:[~2024-04-09 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 11:15 Nirmoy Das [this message]
2024-04-09 11:31 ` [PATCH] drm/i915: Use enum mode in drm_mm_insert_node_in_range Matthew Auld
2024-04-09 11:33 ` Matthew Auld
2024-04-09 11:36 ` Nirmoy Das
2024-04-09 11:49 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-09 11:49 ` ✓ CI.checkpatch: " Patchwork
2024-04-09 11:50 ` ✓ CI.KUnit: " Patchwork
2024-04-09 12:02 ` ✓ CI.Build: " Patchwork
2024-04-09 12:04 ` ✓ CI.Hooks: " Patchwork
2024-04-09 12:06 ` ✓ CI.checksparse: " Patchwork
2024-04-09 12:30 ` ✗ CI.BAT: failure " Patchwork
2024-04-09 14:32 ` ✓ CI.FULL: success " 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=20240409111541.2478-1-nirmoy.das@intel.com \
--to=nirmoy.das@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@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;
as well as URLs for NNTP newsgroup(s).