linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	vincent.guittot@linaro.org, rostedt@goodmis.org,
	dietmar.eggemann@arm.com, bristot@redhat.com, bsegall@google.com,
	mgorman@suse.de, Mark Simmons <msimmons@redhat.com>
Subject: Re: [PATCH] sched/rt: Fix double enqueue caused by rt_effective_prio
Date: Fri, 9 Jul 2021 10:33:18 +0200	[thread overview]
Message-ID: <YOgJzqOrVHUvCpch@localhost.localdomain> (raw)
In-Reply-To: <YObS2Rudg4osS7Ic@hirez.programming.kicks-ass.net>

Hi Peter,

On 08/07/21 12:26, Peter Zijlstra wrote:
> On Thu, Jul 08, 2021 at 12:06:27PM +0200, Peter Zijlstra wrote:
> > Slightly larger patch, but perhaps a little cleaner.. still pondering if
> > we can share a little more between __sched_setscheduler() and
> > rt_mutex_setprio().
> 
> Best I can seem to come up with...

Thanks for the non-lazy version of the fix!

Makes sense to me and it looks good from quick testing. I'll be doing
more extensive testing and ask Mark (cc-ed) to help with that. :)

We'll report back soon-ish.

Best,
Juri


  reply	other threads:[~2021-07-09  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  9:14 [PATCH] sched/rt: Fix double enqueue caused by rt_effective_prio Juri Lelli
2021-07-06 14:48 ` Dietmar Eggemann
2021-07-07  8:47   ` Juri Lelli
2021-07-08 10:06 ` Peter Zijlstra
2021-07-08 10:26   ` Peter Zijlstra
2021-07-09  8:33     ` Juri Lelli [this message]
2021-08-02  7:35       ` Juri Lelli
2021-08-02 13:38         ` Peter Zijlstra
2021-07-08 11:35 ` Peter Zijlstra

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=YOgJzqOrVHUvCpch@localhost.localdomain \
    --to=juri.lelli@redhat.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=msimmons@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).