From: Tejun Heo <tj@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
rusty@rustcorp.com.au, paulus@samba.org, acme@redhat.com,
Paul Menage <menage@google.com>
Subject: Re: [PATCH UPDATED 2/4] sched: adjust when cpu_active and cpuset configurations are updated during cpu on/offlining
Date: Fri, 04 Jun 2010 14:03:00 +0200 [thread overview]
Message-ID: <4C08EB74.8070300@kernel.org> (raw)
In-Reply-To: <1275652701.27810.39745.camel@twins>
On 06/04/2010 01:58 PM, Peter Zijlstra wrote:
>> * Rollback on failure.
>>
>> * cpuset/sched_domain don't expect to be called before smp
>> configuration is complete. If hardcoded into cpu_up/down(),
>> condition checks need to be added so that they're skipped if the
>> system is bringing up the cpus for the first time.
>>
>> Works fine here w/ CPUSET enabled and disabled.
>
> OK, this looks good.
Cool, can I add your acked-by's to and send them towards Ingo?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-06-04 12:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 18:56 [PATCHSET sched/core] sched: prepare for cmwq, take#2 Tejun Heo
2010-05-31 18:56 ` [PATCH 1/4] sched: define and use CPU_PRI_* enums for cpu notifier priorities Tejun Heo
2010-05-31 18:56 ` [PATCH 2/4] sched: adjust when cpu_active and cpuset configurations are updated during cpu on/offlining Tejun Heo
2010-06-01 15:57 ` Peter Zijlstra
2010-06-01 16:58 ` Tejun Heo
2010-06-01 17:20 ` Peter Zijlstra
2010-06-02 16:03 ` [PATCH UPDATED " Tejun Heo
2010-06-04 7:43 ` Tejun Heo
2010-06-04 11:58 ` Peter Zijlstra
2010-06-04 12:03 ` Tejun Heo [this message]
2010-06-04 12:07 ` Peter Zijlstra
2010-05-31 18:56 ` [PATCH 3/4] sched: refactor try_to_wake_up() Tejun Heo
2010-05-31 18:56 ` [PATCH 4/4] sched: add hooks for workqueue Tejun Heo
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=4C08EB74.8070300@kernel.org \
--to=tj@kernel.org \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
/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).