All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: robin.clark@oss.qualcomm.com, lumag@kernel.org
Cc: abhinav.kumar@linux.dev, jessica.zhang@oss.qualcomm.com,
	sean@poorly.run, marijn.suijten@somainline.org,
	airlied@gmail.com, simona@ffwll.ch, antomani103@gmail.com,
	linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Sasha Levin <sashal@kernel.org>
Subject: [PATCH] drm/msm: Fix objtool warning in submit_lock_objects()
Date: Tue,  5 Aug 2025 18:55:57 -0400	[thread overview]
Message-ID: <20250805225557.593192-1-sashal@kernel.org> (raw)

Restructure submit_lock_objects() to use a single loop with break
statements to fix objtool warning:

  drivers/gpu/drm/msm/msm.o: warning: objtool: submit_lock_objects+0x451:
  sibling call from callable instruction with modified stack frame

The drm_exec_until_all_locked() macro uses computed gotos internally
for its retry loop. Having return statements inside this macro, or
immediately after it in certain code paths, confuses objtool's static
analysis of stack frames, causing it to incorrectly flag tail call
optimizations.

Fixes: 92395af63a99 ("drm/msm: Add VM_BIND submitqueue")
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 drivers/gpu/drm/msm/msm_gem_submit.c | 43 ++++++++++++----------------
 1 file changed, 19 insertions(+), 24 deletions(-)

diff --git a/drivers/gpu/drm/msm/msm_gem_submit.c b/drivers/gpu/drm/msm/msm_gem_submit.c
index 5f8e939a5906..253347b6e328 100644
--- a/drivers/gpu/drm/msm/msm_gem_submit.c
+++ b/drivers/gpu/drm/msm/msm_gem_submit.c
@@ -276,46 +276,41 @@ static int submit_lock_objects(struct msm_gem_submit *submit)
 {
 	unsigned flags = DRM_EXEC_INTERRUPTIBLE_WAIT;
 	struct drm_exec *exec = &submit->exec;
-	int ret;
+	int ret = 0;
 
-	if (msm_context_is_vmbind(submit->queue->ctx)) {
+	if (msm_context_is_vmbind(submit->queue->ctx))
 		flags |= DRM_EXEC_IGNORE_DUPLICATES;
 
-		drm_exec_init(&submit->exec, flags, submit->nr_bos);
+	drm_exec_init(&submit->exec, flags, submit->nr_bos);
 
-		drm_exec_until_all_locked (&submit->exec) {
+	drm_exec_until_all_locked (&submit->exec) {
+		if (msm_context_is_vmbind(submit->queue->ctx)) {
 			ret = drm_gpuvm_prepare_vm(submit->vm, exec, 1);
 			drm_exec_retry_on_contention(exec);
 			if (ret)
-				return ret;
+				break;
 
 			ret = drm_gpuvm_prepare_objects(submit->vm, exec, 1);
 			drm_exec_retry_on_contention(exec);
 			if (ret)
-				return ret;
-		}
-
-		return 0;
-	}
-
-	drm_exec_init(&submit->exec, flags, submit->nr_bos);
-
-	drm_exec_until_all_locked (&submit->exec) {
-		ret = drm_exec_lock_obj(&submit->exec,
-					drm_gpuvm_resv_obj(submit->vm));
-		drm_exec_retry_on_contention(&submit->exec);
-		if (ret)
-			return ret;
-		for (unsigned i = 0; i < submit->nr_bos; i++) {
-			struct drm_gem_object *obj = submit->bos[i].obj;
-			ret = drm_exec_prepare_obj(&submit->exec, obj, 1);
+				break;
+		} else {
+			ret = drm_exec_lock_obj(&submit->exec,
+						drm_gpuvm_resv_obj(submit->vm));
 			drm_exec_retry_on_contention(&submit->exec);
 			if (ret)
-				return ret;
+				break;
+			for (unsigned i = 0; i < submit->nr_bos; i++) {
+				struct drm_gem_object *obj = submit->bos[i].obj;
+				ret = drm_exec_prepare_obj(&submit->exec, obj, 1);
+				drm_exec_retry_on_contention(&submit->exec);
+				if (ret)
+					break;
+			}
 		}
 	}
 
-	return 0;
+	return ret;
 }
 
 static int submit_fence_sync(struct msm_gem_submit *submit)
-- 
2.39.5


             reply	other threads:[~2025-08-05 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 22:55 Sasha Levin [this message]
2025-08-06 23:38 ` [PATCH] drm/msm: Fix objtool warning in submit_lock_objects() Rob Clark
2025-08-07 13:03   ` Sasha Levin

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=20250805225557.593192-1-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=abhinav.kumar@linux.dev \
    --cc=airlied@gmail.com \
    --cc=antomani103@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jessica.zhang@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    /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.