public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: alix.wu@mediatek.com, "joe.liu" <joe.liu@mediatek.com>,
	ltp@lists.linux.it, xufeifei1@oppo.com
Subject: Re: [LTP] [PATCH v2] sched: starvation: Autocallibrate the timeout
Date: Wed, 10 Jul 2024 17:55:21 +0200	[thread overview]
Message-ID: <20240710155521.GC300896@pevik> (raw)
In-Reply-To: <ZoQTD_QLwP8w9sPe@yuki>

Hi Cyril,
all,

> Hi!
> > > What kernel version do you use?
> > We are now using kernel 5.15

> > > Do you run LTP with background tasks to keep the CPU bussy?
> > Yes, we are testing LTP with Android VTS. And the test environment is under Android Launcher.

> > > Do you have any custom patches for kernel scheduller applied?
> > I think there is no any patch applied for kernel scheduller.

> > > It really looks like something unexpected is happening at your end.

> > Actually, the same kernel version using 64bit kernel can pass the ltp test.



> > 1. for 32bit kernel, we have this log

> > 32bit kernel
> > external/ltp/testcases/kernel/sched/cfs-scheduler/starvation.c:161: TINFO: do_test by pid 4523
> > external/ltp/testcases/kernel/sched/cfs-scheduler/starvation.c:166: TINFO: main pid is 4523
> > external/ltp/testcases/kernel/sched/cfs-scheduler/starvation.c:167: TINFO: child pid is 4524
> > external/ltp/testcases/kernel/sched/cfs-scheduler/starvation.c:166: TINFO: main pid is 4524
> > external/ltp/testcases/kernel/sched/cfs-scheduler/starvation.c:167: TINFO: child pid is 0
> > external/ltp/testcases/kernel/sched/cfs-scheduler/starvation.c:176: TINFO: go loop, current pid is 4523
> > external/ltp/testcases/kernel/sched/cfs-scheduler/starvation.c:145: TINFO: current ppid is 4523, current pid is 4524, go to child() start

> > main pid is 4523, child pid is 4524, and we only see child pid is working (checking by top)

> > 4524 root         20   0  14M 472K    0 R 85.7   0.0   0:14.93 starvation_v4 -t 1000000 -l 1000000 <-- cpu_load by top

> So this looks like we managed to reproduce the issue the test was trying
> to catch. The child is hogging the CPU and the parent process cannot
> proceed. And I suppose that this happens only on 32bit because 32bit is
> less tested these days.

I guess we can merge this, right?
Or we still not sure whether this is really kernel bug not related to the
change?

Kind regards,
Petr

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

  reply	other threads:[~2024-07-10 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 11:23 [LTP] [PATCH v2] sched: starvation: Autocallibrate the timeout Cyril Hrubis
2024-06-12 12:21 ` Petr Vorel
2024-06-12 18:22   ` Cyril Hrubis
2024-06-13 11:22 ` Anders Roxell
2024-06-27  9:28 ` joe.liu via ltp
2024-06-28 12:49   ` Cyril Hrubis
2024-07-01  9:50 ` joe.liu via ltp
2024-07-02 14:47   ` Cyril Hrubis
2024-07-10 15:55     ` Petr Vorel [this message]
2024-07-10 18:12       ` Cyril Hrubis

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=20240710155521.GC300896@pevik \
    --to=pvorel@suse.cz \
    --cc=alix.wu@mediatek.com \
    --cc=chrubis@suse.cz \
    --cc=joe.liu@mediatek.com \
    --cc=ltp@lists.linux.it \
    --cc=xufeifei1@oppo.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