mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: jemmywong512@gmail.com
Cc: sh_def@163.com, jstultz@google.com, bsegall@google.com,
	dietmar.eggemann@arm.com, juri.lelli@redhat.com,
	kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
	mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
	rostedt@goodmis.org, tim.c.chen@linux.intel.com,
	vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [PATCH 0/3] sched: Fix proxy-exec use of curr and donor
Date: Thu,  8 Oct 2026 18:33:48 +0300	[thread overview]
Message-ID: <20261008153348.92684-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <20261008132604.98242-1-jemmywong512@gmail.com>

> After the split between scheduling and execution context, update_se()
> charges the open run interval to rq->curr. The tick and the runtime
> sample still treated the donor as the task on CPU. Under proxy
> execution the donor is blocked on a kernel mutex and the lock holder
> is the task that runs.

Please look at here: https://lore.kernel.org/lkml/20260913064722.1534766-1-sh_def@163.com/

I think y'all are trying to fix the same thing, no? (Or atleast similar in most ways.)

Adding Hui and John to CC.

Thanks,
Kayra

  parent reply	other threads:[~2026-10-08 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 13:26 Jemmy Wong
2026-10-08 13:26 ` [PATCH 1/3] sched/fair: Drive NUMA and cache tick work from the execution context Jemmy Wong
2026-10-08 13:26 ` [PATCH 2/3] sched/core: Flush pending runtime for " Jemmy Wong
2026-10-08 13:26 ` [PATCH 3/3] sched/core: Check CFS bandwidth against the donor for NOHZ Jemmy Wong
2026-10-08 15:33 ` Kayra Cizmeci [this message]
2026-10-09  3:41   ` [PATCH 0/3] sched: Fix proxy-exec use of curr and donor Jemmy Wong
2026-10-09  4:07     ` Hui Su
2026-10-09  5:46       ` Jemmy Wong

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=20261008153348.92684-1-kayracizmeci@gmail.com \
    --to=kayracizmeci@gmail.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jemmywong512@gmail.com \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sh_def@163.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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®