public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@arm.com>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>
Cc: "juri.lelli@gmail.com" <juri.lelli@gmail.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"vincent@legout.info" <vincent@legout.info>
Subject: Re: [PATCH 0/4] Fix various bits of AC and PI for SCHED_DEADLINE
Date: Fri, 24 Oct 2014 14:21:14 +0100	[thread overview]
Message-ID: <544A524A.3090305@arm.com> (raw)
In-Reply-To: <544A3949.30305@bmw-carit.de>

Hi Daniel,

On 24/10/14 12:34, Daniel Wagner wrote:
> Hi everyone,
> 
> On 10/24/2014 11:16 AM, Juri Lelli wrote:
>> Hi all,
>>
>> this is basically a resend of 4 patches fixing problems around AC
>> and PI related to SCHED_DEADLINE. You can find the full story here:
>>
>>  - https://lkml.org/lkml/2014/9/19/134
>>  - https://lkml.org/lkml/2014/9/24/493
>>
>> First two patches fix AC. They are the same as the previous version,
>> plus aligning to commit f10e00f4bf36 ("sched/dl: Use dl_bw_of() under
>> rcu_read_lock_sched()"). Last two fix PI.
>>
>> Thanks a lot again to Daniel for spending time fixing and testing
>> the PI stuff! And to Peter and Vincent for reviews and comments.
> 
> Thanks for the patches!
> 
>> Best Regards,
>>
>> - Juri
>>
>> Juri Lelli (4):
>>   sched/deadline: fix bandwidth check/update when migrating tasks
>>     between exclusive cpusets
>>   sched/deadline: ensure that updates to exclusive cpusets don't break
>>     AC
>>   sched/deadline: don't replenish from a !SCHED_DEADLINE entity
>>   sched/deadline: fix races between rt_mutex_setprio and dl_task_timer
> 
> I have tested the whole patch set with my test program and everything
> seems to work fine. If you like you can add a
> 

Cool! Thanks a lot.

> Tested-by: Daniel Wagner <daniel.wagner@bmw-carit.de>
> 

Peter, maybe you can add it while applying them?

Thanks,

- Juri


  reply	other threads:[~2014-10-24 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  9:16 [PATCH 0/4] Fix various bits of AC and PI for SCHED_DEADLINE Juri Lelli
2014-10-24  9:16 ` [PATCH 1/4] sched/deadline: fix bandwidth check/update when migrating tasks between exclusive cpusets Juri Lelli
2014-10-24  9:16 ` [PATCH 2/4] sched/deadline: ensure that updates to exclusive cpusets don't break AC Juri Lelli
2014-10-24  9:16 ` [PATCH 3/4] sched/deadline: don't replenish from a !SCHED_DEADLINE entity Juri Lelli
2014-10-28 11:01   ` [tip:sched/core] sched/deadline: Don' t " tip-bot for Juri Lelli
2014-10-24  9:16 ` [PATCH 4/4] sched/deadline: fix races between rt_mutex_setprio and dl_task_timer Juri Lelli
2014-10-28 11:02   ` [tip:sched/core] sched/deadline: Fix races between rt_mutex_setprio() and dl_task_timer() tip-bot for Juri Lelli
2014-10-24 11:34 ` [PATCH 0/4] Fix various bits of AC and PI for SCHED_DEADLINE Daniel Wagner
2014-10-24 13:21   ` Juri Lelli [this message]
2014-10-24 13:39     ` 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=544A524A.3090305@arm.com \
    --to=juri.lelli@arm.com \
    --cc=daniel.wagner@bmw-carit.de \
    --cc=juri.lelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=vincent@legout.info \
    /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