From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Konstantin Khlebnikov <khlebnikov@openvz.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Prashanth Nageshappa <prashanth@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Subject: Re: [PATCH bisected regression] sched: rebuild sched domains at suspend/resume
Date: Tue, 24 Apr 2012 19:15:00 +0200 [thread overview]
Message-ID: <1335287700.28150.211.camel@twins> (raw)
In-Reply-To: <4F9555C5.6040601@linux.vnet.ibm.com>
On Mon, 2012-04-23 at 18:44 +0530, Srivatsa S. Bhat wrote:
>
> Basically, our assumption that we are good to go (even with stale sched
> domains) as long as the dying cpu was not in the cpu_active_mask, was wrong.
Argh, that means cpu_active_mask is pointless.. so we should either fix
that or remove that thing entirely.
Anyway, tglx is reworking all that hotplug stuff as we speak, I think
its best to wait for that dust to settle before we go make the mess even
bigger.
next prev parent reply other threads:[~2012-04-24 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 20:45 [PATCH bisected regression] sched: rebuild sched domains at suspend/resume Konstantin Khlebnikov
2012-03-06 21:02 ` Peter Zijlstra
2012-03-06 21:47 ` Konstantin Khlebnikov
2012-03-07 0:54 ` Linus Torvalds
2012-03-07 1:38 ` Peter Zijlstra
2012-03-07 1:42 ` Linus Torvalds
2012-03-11 19:44 ` Konstantin Khlebnikov
2012-03-12 11:22 ` Thomas Gleixner
2012-03-12 11:56 ` Srivatsa S. Bhat
2012-04-23 13:14 ` Srivatsa S. Bhat
2012-04-24 17:15 ` Peter Zijlstra [this message]
2012-03-07 13:34 ` Srivatsa S. Bhat
2012-03-07 14:02 ` Ingo Molnar
2012-03-07 15:40 ` Konstantin Khlebnikov
2012-03-07 15:49 ` Srivatsa S. Bhat
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=1335287700.28150.211.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nikunj@linux.vnet.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=prashanth@linux.vnet.ibm.com \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vatsa@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.