public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] sched_rr_get_interval01 , sched_rr_get_interval02 , sched_rr_get_interval03 testcase failure
Date: Tue, 9 Jun 2020 02:48:48 -0400 (EDT)	[thread overview]
Message-ID: <1242963582.15267570.1591685328616.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <BMXPR01MB23445D894481BDFED050AD27EE820@BMXPR01MB2344.INDPRD01.PROD.OUTLOOK.COM>

----- Original Message ----- 

> sched_setscheduler(0, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted)

Thanks, that aligns with the theory.

> 2)
> root@exaleapsemi-r2:/opt/ltp# pu_mnt=$(mount | grep "type cgroup (.*cpu[,)]"
> | awk '{print $3}')
> root@exaleapsemi-r2:/opt/ltp# cpu_mnt=$(mount | grep "type cgroup (.*cpu[,)]"
> | awk '{print $3}')
> root@exaleapsemi-r2:/opt/ltp# p=$(cat /proc/self/cgroup | grep ":cpu[:,]" |
> sed "s/.*://")
> root@exaleapsemi-r2:/opt/ltp# cat $cpu_mnt/$p/cpu.rt_runtime_us
> cat: //system.slice/system-sshd.slice/cpu.rt_runtime_us: No such file or
> directory

> it didnt gave any info about cpu.rt_runtime_us??

That could be because your distro is mounting cgroup2.

# mount | grep cgroup

Do you see any change if you run following?

# echo $$ > /sys/fs/cgroup/cgroup.procs
# /opt/ltp/testcases/bin/sched_setparam02


      reply	other threads:[~2020-06-09  6:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 12:19 [LTP] sched_rr_get_interval01 , sched_rr_get_interval02 , sched_rr_get_interval03 testcase failure Pankaj Vinadrao Joshi
2020-06-08 14:52 ` Jan Stancek
     [not found]   ` <BMXPR01MB2344728D919729E8F7F007EBEE820@BMXPR01MB2344.INDPRD01.PROD.OUTLOOK.COM>
2020-06-09  6:25     ` Jan Stancek
2020-06-09  6:39       ` Pankaj Vinadrao Joshi
2020-06-09  6:48         ` Jan Stancek [this message]

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=1242963582.15267570.1591685328616.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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