From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Len Brown <lenb@kernel.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: clockevents: fix resume logic
Date: Tue, 11 Sep 2007 20:38:03 +0200 [thread overview]
Message-ID: <1189535883.5235.13.camel@chaos> (raw)
In-Reply-To: <20070911112531.80bac380.akpm@linux-foundation.org>
On Tue, 2007-09-11 at 11:25 -0700, Andrew Morton wrote:
> > It evidently assumes cpuidle to be present, which is not in the mainline.
>
> Bear in mind that the cpuidle patch fixes resume-from-ram when cpuidle is
> disabled in config.
>
> > It seems to me that the total effect of this one and the hackpatch is that
> > the C states are not handled any more.
>
> hm.
>
> dmesg without the cpuidle patch: http://userweb.kernel.org/~akpm/dmesg-bad.txt
> dmesg with the cpuidle patch: http://userweb.kernel.org/~akpm/dmesg-good.txt
> difference: http://userweb.kernel.org/~akpm/dmesg-diff.txt
>
> there doesn't seem to be a lot of difference in the time handling, except
> there are large changes in when things happen in the bootup sequence.
The question is whether the system goes into C2 with the patch applied.
Can you please provide the output of /proc/acpi/processor/CPU0/power for
both the bad and the good one ?
tglx
next prev parent reply other threads:[~2007-09-11 18:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707220159.l6M1xBgH001236@hera.kernel.org>
2007-09-10 21:47 ` clockevents: fix resume logic Andrew Morton
2007-09-11 6:37 ` Thomas Gleixner
2007-09-11 7:00 ` Andrew Morton
2007-09-11 7:23 ` Thomas Gleixner
2007-09-11 7:34 ` Thomas Gleixner
2007-09-11 7:44 ` Andrew Morton
2007-09-11 7:47 ` Thomas Gleixner
2007-09-11 8:20 ` Andrew Morton
2007-09-11 8:35 ` Andrew Morton
2007-09-11 9:16 ` Thomas Gleixner
2007-09-11 10:31 ` Andrew Morton
2007-09-11 11:23 ` Rafael J. Wysocki
2007-09-11 11:22 ` Andrew Morton
2007-09-11 12:09 ` Rafael J. Wysocki
2007-09-11 18:25 ` Andrew Morton
2007-09-11 18:38 ` Thomas Gleixner [this message]
2007-09-11 18:44 ` Andrew Morton
2007-09-11 19:52 ` Thomas Gleixner
2007-09-11 21:49 ` Thomas Gleixner
2007-09-12 9:16 ` Andrew Morton
2007-09-12 16:57 ` Thomas Gleixner
2007-09-13 4:48 ` Andrew Morton
2007-09-12 9:12 ` Andrew Morton
2007-09-17 18:37 ` Pavel Machek
2007-09-22 8:50 ` Thomas Gleixner
2007-09-22 10:47 ` Rafael J. Wysocki
2007-10-02 8:05 ` Pavel Machek
2007-09-11 19:35 ` Rafael J. Wysocki
2007-09-11 19:39 ` Andrew Morton
2007-09-11 19:40 ` Arjan van de Ven
2007-09-11 9:01 ` Thomas Gleixner
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=1189535883.5235.13.camel@chaos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=venkatesh.pallipadi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox