From: Thomas Gleixner <tglx@linutronix.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Jeff Chua <jeff.chua.linux@gmail.com>,
rusty@rustycorp.com.au, vatsa@in.ibm.com, zwane@arm.linux.org.uk,
kernel list <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: RE: cpu hotplug support broken in 2.6.23-rc3
Date: Fri, 14 Sep 2007 21:18:03 +0200 [thread overview]
Message-ID: <1189797483.3707.3.camel@chaos> (raw)
In-Reply-To: <653FFBB4508B9042B5D43DC9E18836F501619542@scsmsx415.amr.corp.intel.com>
On Fri, 2007-09-14 at 11:49 -0700, Pallipadi, Venkatesh wrote:
> >>
> >> Is there a patch you want me to test? Or does Len have anything to
> >> play with?
> >
> >Venki sent me an initial patch, but it has issues with the notify
> >ordering. Find below my "cache the broadcast flags" version
> >for testing.
> >
>
> While wirting that patch, I knew solution could not be that simple :(.
> Does the patch work for online offline case atleast?
> Will look at the Suspend/Resume ordering part in that case.
Yup, the online/offline part works and it helped me to decode the other
reason (/me needs a dark brown paperbag) why Pavel noticed that his box
turned into a brick. I'll send out a full series of fixups (including
your online/offline one) tomorrow morning. I want to give that some more
testing.
Vs. the resume reevaluation: I don't think it's an urgent problem. It's
only my VAIO which does not tell the kernel after resume that the power
supply source has changed. All my other boxen do that and we never had a
complaint about that from other folks.
tglx
next prev parent reply other threads:[~2007-09-14 19:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 10:43 cpu hotplug support broken in 2.6.23-rc3 Pavel Machek
2007-08-27 10:58 ` Pavel Machek
2007-08-27 14:36 ` Jeff Chua
2007-08-27 15:22 ` Michal Piotrowski
2007-08-27 21:32 ` Pavel Machek
2007-08-27 21:59 ` Rafael J. Wysocki
2007-08-27 21:58 ` Pavel Machek
2007-08-28 10:30 ` Rafael J. Wysocki
2007-08-28 13:00 ` Akinobu Mita
2007-08-28 14:21 ` Jeff Chua
2007-09-03 3:47 ` Pavel Machek
2007-09-03 10:19 ` Rafael J. Wysocki
2007-09-03 12:35 ` Thomas Gleixner
2007-09-04 7:27 ` Pavel Machek
2007-09-13 20:01 ` Thomas Gleixner
2007-09-14 12:38 ` Pavel Machek
2007-09-14 12:50 ` Thomas Gleixner
2007-09-14 13:15 ` Thomas Gleixner
2007-09-15 9:49 ` Thomas Gleixner
2007-09-15 10:18 ` Andrew Morton
2007-09-15 13:28 ` Thomas Gleixner
2007-09-15 22:01 ` Andrew Morton
2007-09-15 13:44 ` Thomas Gleixner
2007-10-02 9:45 ` Pavel Machek
2007-09-14 18:49 ` Pallipadi, Venkatesh
2007-09-14 19:18 ` Thomas Gleixner [this message]
2007-09-03 3:56 ` highres timers break cpu hotplug in 2.6.23-rc5 [was Re: cpu hotplug support broken in 2.6.23-rc3] Pavel Machek
2007-09-03 12:34 ` Jeff Chua
2007-08-29 8:08 ` cpu hotplug support broken in 2.6.23-rc3 Gautham R Shenoy
2007-09-03 3:58 ` Pavel Machek
2007-11-15 22:37 ` cpu hotplug strangeness in 2.6.24-rc2 (was Re: cpu hotplug support broken in 2.6.23-rc3) Pavel Machek
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=1189797483.3707.3.camel@chaos \
--to=tglx@linutronix.de \
--cc=jeff.chua.linux@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=rusty@rustycorp.com.au \
--cc=vatsa@in.ibm.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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