mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Xuewen Yan <xuewen.yan94@gmail.com>
Cc: "Vincent Guittot" <vincent.guittot@linaro.org>,
	"John Stultz" <jstultz@google.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Juri Lelli" <juri.lelli@redhat.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Benjamin Segall" <bsegall@google.com>,
	"Mel Gorman" <mgorman@suse.de>,
	"Valentin Schneider" <vschneid@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"王科 (Ke Wang)" <Ke.Wang@unisoc.com>,
	"Xuewen Yan" <xuewen.yan@unisoc.com>,
	"hongyu.jin@unisoc.com" <hongyu.jin@unisoc.com>,
	guohua.yan@unisoc.com
Subject: Re: [Question] Sched: Severe scheduling latency (>10s) observed on kernel 6.12 with specific workload
Date: Tue, 14 Apr 2026 16:49:11 +0100	[thread overview]
Message-ID: <d814a498-72fd-4ec8-be8c-2cdb5e1f349e@arm.com> (raw)
In-Reply-To: <CAB8ipk_ea+c5__G3vYCsQznzU_CvjdY3SMQEBpv-KXyitSGznw@mail.gmail.com>

On 14.04.26 06:18, Xuewen Yan wrote:
> Thanks Dietmar!
> 
> On Fri, Apr 10, 2026 at 7:14 PM Dietmar Eggemann
> <dietmar.eggemann@arm.com> wrote:
>>
>> On 08.04.26 03:50, Xuewen Yan wrote:
>>> Hi Dietmar and Vincent,

[...]

> We tested in Android tree without any vendorhooks.
> Just as John said, after we revert commit 6d71a9c61604 ("sched/fair:
> Fix EEVDF entity
> placement bug causing scheduling lag") in android16-6.12, the latency
> disappeared, because the commit is not exist in stable tree.
> 
> On the other hand, we also tested the android17-6.18, without any
> revert, the latency still exist.

So it's not about the wu_lat of the rt-app tasks but the latency values
of the cyclictest tasks?

cyclictest -m -t -a --policy=SCHED_OTHER -b 1000000 -D
120s

[...]

  reply	other threads:[~2026-04-14 15:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAB8ipk9N5_pO1Awp6PLnWt6hf1Bu_XtY3qGMJKqz=Uf6eZQejw@mail.gmail.com>
2026-04-01  4:25 ` John Stultz
2026-04-01  6:04   ` Xuewen Yan
2026-04-01 10:05     ` Vincent Guittot
2026-04-01 10:48       ` Xuewen Yan
2026-04-01 13:00         ` Dietmar Eggemann
2026-04-02  5:16           ` Xuewen Yan
2026-04-02 14:58             ` Dietmar Eggemann
2026-04-08  2:50               ` Xuewen Yan
2026-04-10 11:13                 ` Dietmar Eggemann
2026-04-14  5:18                   ` Xuewen Yan
2026-04-14 15:49                     ` Dietmar Eggemann [this message]
2026-04-01 14:01         ` Vincent Guittot
2026-04-02  5:11           ` Xuewen Yan
2026-04-02  5:24             ` Xuewen Yan
2026-04-08 12:19 ` David Laight
2026-04-09 21:39 ` John Stultz
2026-04-10  3:31   ` Xuewen Yan
2026-04-10  4:01     ` John Stultz
2026-04-10 12:24       ` Dietmar Eggemann
2026-04-13 20:44       ` John Stultz
2026-04-14 15:43         ` Dietmar Eggemann
2026-04-14 19:21           ` John Stultz

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=d814a498-72fd-4ec8-be8c-2cdb5e1f349e@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=Ke.Wang@unisoc.com \
    --cc=bsegall@google.com \
    --cc=guohua.yan@unisoc.com \
    --cc=hongyu.jin@unisoc.com \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=xuewen.yan94@gmail.com \
    --cc=xuewen.yan@unisoc.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®