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>,
	Vincent Guittot <vincent.guittot@linaro.org>
Cc: "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: Wed, 1 Apr 2026 15:00:04 +0200	[thread overview]
Message-ID: <1c0e5a70-22b7-4cbd-8ca9-0a7da27ed7a9@arm.com> (raw)
In-Reply-To: <CAB8ipk_tzb97ZPMM8heRkEyNC1swF3qbuPpP2Yv-9bExZhGJQQ@mail.gmail.com>

On 01.04.26 12:48, Xuewen Yan wrote:
> On Wed, Apr 1, 2026 at 6:05 PM Vincent Guittot
> <vincent.guittot@linaro.org> wrote:
>>
>> On Wed, 1 Apr 2026 at 08:04, Xuewen Yan <xuewen.yan94@gmail.com> wrote:
>>>
>>> On Wed, Apr 1, 2026 at 12:25 PM John Stultz <jstultz@google.com> wrote:
>>>>
>>>> On Tue, Mar 31, 2026 at 7:32 PM Xuewen Yan <xuewen.yan94@gmail.com> wrote:
>>>>>
>>>>> Dear Linux maintainers and reviewers,
>>>>>
>>>>> I am writing to report a severe scheduling latency issue we recently
>>>>> discovered on Linux Kernel 6.12.
>>>>>
>>>>> Issue Description
>>>>>
>>>>> We observed that when running a specific background workload pattern,
>>>>> certain tasks experience excessive scheduling latency. The delay from
>>>>> the runnable state to running on the CPU exceeds 10 seconds, and in
>>>>> extreme cases, it reaches up to 100 seconds.
>>>>>
>>>>> Environment Details
>>>>>
>>>>> Kernel Version: 6.12.58-android16-6-g3835fd28159d-ab000018-4k
>>>>> Architecture: [ ARM64]
>>>>> Hardware: T7300

Is this 4 big & 4 little CPUs?

>>>>> Config: gki_defconfig
>>>>>
>>>>> RT-app‘s workload Pattern:
>>>>>
>>>>> {
>>>>>     "tasks" : {
>>>>>             "t0" : {
>>>>>                     "instance" : 40,
>>>>>                     "priority" : 0,
>>>>>                     "cpus" : [ 0, 1, 2, 3 ],
>>>>> "taskgroup" : "/background",
>>>>>                     "loop" : -1,
>>>>>                     "run" : 200,
>>>>>                     "sleep" : 50
>>>>>             }
>>>>>     }
>>>>> }
>>>>>
>>>>> And we have applied the following patchs:
>>>>>
>>>>> https://lore.kernel.org/all/20251216111321.966709786@linuxfoundation.org/
>>>>> https://lore.kernel.org/all/20260106170509.413636243@linuxfoundation.org/
>>>>> https://lore.kernel.org/all/20260323134533.805879358@linuxfoundation.org/

Does the issue happen on v6.12.58 plain (android) or only when those 3
additional patches are applied on top?

d5843e1530d8 - sched/fair: Forfeit vruntime on yield (2025-12-18 Fernand
Sieber) v6.12.63

bddd95054e33 - sched/eevdf: Fix min_vruntime vs avg_vruntime (2026-01-08
Peter Zijlstra) v6.12.64

d2fc2dcfce47 - sched/fair: Fix zero_vruntime tracking (2026-03-25 Peter
Zijlstra) v6.12.78

[...]

  reply	other threads:[~2026-04-01 13:00 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 [this message]
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
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=1c0e5a70-22b7-4cbd-8ca9-0a7da27ed7a9@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®