mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuele Mariotti <smariotti@disroot.org>
To: tj@kernel.org
Cc: void@manifault.com, arighi@nvidia.com, changwoo@igalia.com,
	jpiecuch@google.com, shuah@kernel.org, sched-ext@lists.linux.dev,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Samuele Mariotti <smariotti@disroot.org>
Subject: [PATCH] selftests/sched_ext: Fix build error in dequeue_remote selftest
Date: Mon, 12 Oct 2026 13:59:28 +0200	[thread overview]
Message-ID: <20261012115928.1372317-1-smariotti@disroot.org> (raw)

Building the dequeue_remote selftest with newer compilers (e.g., gcc 16)
triggers the following error:

dequeue_remote.c:39:32: error: variable ‘sum’ set but not used

The 'volatile' qualifier prevents the writes from being optimized away,
but does not silence the warning, since 'sum' is indeed only written and
never read.

Consume 'sum' via an empty asm() with a register input constraint, as
already done for the dequeue selftest in commit 3788e3251653
("selftests/sched_ext: Fix build error in dequeue selftest"). This forces
the compiler to keep the accumulated value (preserving the CPU stress loop)
and avoids the build error.

Fixes: cc07fae1de5d ("selftests/sched_ext: Add a test for ops.dequeue() on remote local DSQ moves")

Signed-off-by: Samuele Mariotti <smariotti@disroot.org>
---
 tools/testing/selftests/sched_ext/dequeue_remote.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tools/testing/selftests/sched_ext/dequeue_remote.c b/tools/testing/selftests/sched_ext/dequeue_remote.c
index f2c1901030de..af344581d5f1 100644
--- a/tools/testing/selftests/sched_ext/dequeue_remote.c
+++ b/tools/testing/selftests/sched_ext/dequeue_remote.c
@@ -43,6 +43,7 @@ static void worker_fn(int id)
 
 		for (j = 0; j < 20000 + id * 1000; j++)
 			sum += j;
+		asm volatile("" : : "r"(sum));
 		if (id & 1)
 			usleep(100);
 		else
-- 
2.56.0


             reply	other threads:[~2026-10-12 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 11:59 Samuele Mariotti [this message]
2026-10-12 13:17 ` Kuba Piecuch
2026-10-12 18:01 ` Tejun Heo

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=20261012115928.1372317-1-smariotti@disroot.org \
    --to=smariotti@disroot.org \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=jpiecuch@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=sched-ext@lists.linux.dev \
    --cc=shuah@kernel.org \
    --cc=tj@kernel.org \
    --cc=void@manifault.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

all inboxes | Powered by JetHome®