mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hui Su <sh_def@163.com>
To: linux-kernel@vger.kernel.org, sh_def@163.com
Cc: peterz@infradead.org, juri.lelli@redhat.com, mingo@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	vschneid@redhat.com, kprateek.nayak@amd.com, jstultz@google.com,
	connoro@google.com
Subject: Re: [PATCH] sched/rt: Fix RT watchdog accounting for proxy execution
Date: Wed, 09 Sep 2026 18:38:55 +0900	[thread overview]
Message-ID: <0c064defe3ae8a522150ead7ee1980dd.sh_def@163.com> (raw)
In-Reply-To: <20260903111247.3538976-1-sh_def@163.com>

On Thu, Sep 03, 2026 at 07:12:47PM +0800, Hui Su wrote:
> With proxy execution, task_tick_rt() is invoked for the scheduling
> context in rq->donor, while rq->curr identifies the task that is
> actually executing.
>
> Pass rq->curr to watchdog() so these state updates follow the actual
> execution context.

This standalone patch has been superseded by the v4 series. The scheduler
task-tick framework has since been reworked to dispatch both the donor and
execution classes, and the RT watchdog fix has been rebased and folded into
patch 4/5.

The v4 series is available at:

https://lore.kernel.org/r/20260909092901.2989564-1-sh_def@163.com

The task-tick framework redesign was discussed in Peter Zijlstra's review:

https://lore.kernel.org/r/20260908104407.GD687043@noisy.programming.kicks-ass.net

Please consider this standalone patch superseded.

Thanks,
Hui


      reply	other threads:[~2026-09-09  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 11:12 Hui Su
2026-09-09  9:38 ` Hui Su [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=0c064defe3ae8a522150ead7ee1980dd.sh_def@163.com \
    --to=sh_def@163.com \
    --cc=bsegall@google.com \
    --cc=connoro@google.com \
    --cc=dietmar.eggemann@arm.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=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®