From: Juri Lelli <juri.lelli@arm.com>
To: luca abeni <luca.abeni@unitn.it>
Cc: peterz@infradead.org, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH v2] sched/deadline: remove useless param from setup_new_dl_entity
Date: Mon, 4 Jul 2016 10:28:28 +0100 [thread overview]
Message-ID: <20160704092828.GB9218@e106622-lin> (raw)
In-Reply-To: <20160704110324.129bebb4@utopia>
On 04/07/16 11:03, Luca Abeni wrote:
> Hi Juri,
>
> On Wed, 29 Jun 2016 20:07:43 +0100
> Juri Lelli <juri.lelli@arm.com> wrote:
>
> > setup_new_dl_entity() takes two parameters, but it only actually uses
> > one of them, under a different name, to setup a new dl_entity, after:
> >
> > 2f9f3fdc928 "sched/deadline: Remove dl_new from struct
> > sched_dl_entity"
> >
> > as we currently do
> >
> > setup_new_dl_entity(&p->dl, &p->dl)
> >
> > However, before Luca's change we were doing
> >
> > setup_new_dl_entity(dl_se, pi_se)
> >
> > in update_dl_entity() for a dl_se->new entity: we were using pi_se's
> > parameters (the potential PI donor) for setting up a new entity.
> >
> > Restore this behaviour (as we want to correctly initialize parameters
> > of a boosted task that enters DEADLINE) by removing the useless second
> > parameter of setup_new_dl_entity() and retrieving the top waiter
> > directly from inside that function.
> I did not have time to test this patch yet, but it still looks good to
> me.
>
Thanks for reviewing it.
Best,
- Juri
next prev parent reply other threads:[~2016-07-04 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 19:07 [PATCH v2] sched/deadline: remove useless param from setup_new_dl_entity Juri Lelli
2016-07-04 9:03 ` luca abeni
2016-07-04 9:28 ` Juri Lelli [this message]
2016-07-05 7:37 ` Wanpeng Li
2016-07-05 8:52 ` Juri Lelli
2016-07-05 14:20 ` Steven Rostedt
2016-07-05 14:39 ` Juri Lelli
2016-07-05 16:47 ` Steven Rostedt
2016-07-05 16:58 ` Juri Lelli
2016-07-06 8:44 ` luca abeni
2016-07-07 8:39 ` Juri Lelli
2016-07-07 13:47 ` Steven Rostedt
2016-07-08 11:32 ` Juri Lelli
2016-07-06 8:46 ` luca abeni
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=20160704092828.GB9218@e106622-lin \
--to=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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