public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Edward Liaw via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: kernel-team@android.com
Subject: [LTP] [PATCH v5 0/2] sched/starvation: Choose from available cpus
Date: Wed, 19 Jun 2024 16:28:05 +0000	[thread overview]
Message-ID: <20240619162807.2725018-1-edliaw@google.com> (raw)

The starvation test was failing as a 32bit test for some arm
architectures where cpu 0 does not support 32bit applications.

v1: https://lore.kernel.org/ltp/20240605180536.1288027-1-edliaw@google.com/

v2: https://lore.kernel.org/ltp/20240606014022.1425928-1-edliaw@google.com/
Made these substitutions based on Wei's suggestions:
s/TST_EXP_POSITIVE/TST_EXP_PASS
s/TCONF/TBROK

v3: https://lore.kernel.org/ltp/20240606173933.1671989-1-edliaw@google.com/
Substituted test macros with check based on Petr's suggestions.
Split commit into two: first to fix the return code check on
sched_setaffinity.  Second to choose the cpu.

v4: https://lore.kernel.org/ltp/20240613210059.352767-1-edliaw@google.com/
Fixed some typos and commit tags.

v5:
Got the return code check reversed again.  Fixed it.

Edward Liaw via ltp (2):
  sched/starvation: Fix sched_setaffinity return check
  sched/starvation: Choose from available cpus

 .../kernel/sched/cfs-scheduler/starvation.c   | 21 +++++++++++++++++--
 1 file changed, 19 insertions(+), 2 deletions(-)

--
2.45.2.627.g7a2c4fd464-goog


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2024-06-19 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 16:28 Edward Liaw via ltp [this message]
2024-06-19 16:28 ` [LTP] [PATCH v5 1/2] sched/starvation: Fix sched_setaffinity return check Edward Liaw via ltp
2024-06-19 16:28 ` [LTP] [PATCH v5 2/2] sched/starvation: Choose from available cpus Edward Liaw via ltp
2024-06-19 17:50   ` 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=20240619162807.2725018-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