From: Edward Liaw via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: kernel-team@android.com
Subject: [LTP] [PATCH v2] sched/starvation: Choose from available cpus
Date: Thu, 6 Jun 2024 01:40:22 +0000 [thread overview]
Message-ID: <20240606014022.1425928-1-edliaw@google.com> (raw)
From: Edward Liaw via ltp <ltp@lists.linux.it>
Use the first available cpu in the sched_getaffinity set.
This test was failing as a 32bit test for some arm architectures where
cpu 0 does not support 32bit applications.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Signed-off-by: Edward Liaw <edliaw@google.com>
---
.../kernel/sched/cfs-scheduler/starvation.c | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/testcases/kernel/sched/cfs-scheduler/starvation.c b/testcases/kernel/sched/cfs-scheduler/starvation.c
index eb9fd6ff5..0fd45e281 100644
--- a/testcases/kernel/sched/cfs-scheduler/starvation.c
+++ b/testcases/kernel/sched/cfs-scheduler/starvation.c
@@ -49,12 +49,27 @@ again:
static void setup(void)
{
cpu_set_t mask;
+ int cpu = 0;
+ long ncpus = tst_ncpus_conf();
CPU_ZERO(&mask);
- CPU_SET(0, &mask);
+ /* Restrict test to a single cpu */
+ TST_EXP_PASS(sched_getaffinity(0, sizeof(mask), &mask));
- TST_EXP_POSITIVE(sched_setaffinity(0, sizeof(mask), &mask));
+ if (CPU_COUNT(&mask) == 0)
+ tst_brk(TBROK, "No cpus available");
+
+ while (CPU_ISSET(cpu, &mask) == 0 && cpu < ncpus)
+ cpu++;
+
+ CPU_ZERO(&mask);
+
+ CPU_SET(cpu, &mask);
+
+ TST_EXP_PASS(sched_setaffinity(0, sizeof(mask), &mask));
+
+ tst_res(TINFO, "Set affinity to CPU %d", cpu);
if (tst_parse_long(str_loop, &loop, 1, LONG_MAX))
tst_brk(TBROK, "Invalid number of loop number '%s'", str_loop);
--
2.45.1.467.gbab1589fc0-goog
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2024-06-06 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 1:40 Edward Liaw via ltp [this message]
2024-06-06 7:40 ` [LTP] [PATCH v2] sched/starvation: Choose from available cpus Petr Vorel
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=20240606014022.1425928-1-edliaw@google.com \
--to=ltp@lists.linux.it \
--cc=edliaw@google.com \
--cc=kernel-team@android.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