From: john stultz <johnstul@us.ibm.com>
To: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
Cc: Thomas Schlichter <schlicht@uni-mannheim.de>,
"Ronny V. Vindenes" <s864@ii.uib.no>,
Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
cat@zip.com.au, gawain@freda.homelinux.org,
gene.heskett@verizon.net, papadako@csd.uoc.gr
Subject: Re: Terrible interactivity with 2.6.0-t9-mm3
Date: 17 Nov 2003 15:04:32 -0800 [thread overview]
Message-ID: <1069110272.11438.2000.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <1069109719.11424.1994.camel@cog.beaverton.ibm.com>
On Mon, 2003-11-17 at 14:55, john stultz wrote:
> On Mon, 2003-11-17 at 14:51, Prakash K. Cheemplavam wrote:
> > john stultz wrote:
> > > You're correct, I forgot to initialize cpu_khz in the ACPI PM timesource
> > > init code. This patch fixes that.
> >
> > Well I applied your patch without the ones from Thomas Schlichter. Was
> > is intended like that or should it be on top of Thomas patches?
>
> It was to go along side of Thomas' patch. Thomas caught the real issue
> (sched_clock() needs to be switched on use_tsc), but cpu_khz is also
> used in the scheduler, so I just wanted to make sure it was properly set
> as well.
After sending out multiple patches I should have been more clear. Just
to avoid confusion:
* the init_cpu_khz patch goes along side Thomas' patch.
* the more experimental sched_clock() -> monotonic_clock() patch I just
sent out for testing replaces Thomas' patch.
thanks
-john
next prev parent reply other threads:[~2003-11-17 23:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 12:11 Ronny V. Vindenes
2003-11-17 13:12 ` Prakash K. Cheemplavam
2003-11-17 19:46 ` Thomas Schlichter
2003-11-17 21:27 ` john stultz
2003-11-17 22:44 ` john stultz
2003-11-17 22:51 ` Prakash K. Cheemplavam
2003-11-17 22:55 ` john stultz
2003-11-17 23:04 ` john stultz [this message]
2003-11-17 23:46 ` Thomas Schlichter
2003-11-18 22:59 ` linux-2.6.0-test9-mm3_acpi-pm-monotonic-fix_A0 john stultz
2003-11-19 7:34 ` linux-2.6.0-test9-mm3_acpi-pm-monotonic-fix_A0 Thomas Schlichter
2003-11-18 13:24 ` Terrible interactivity with 2.6.0-t9-mm3 Prakash K. Cheemplavam
2003-11-18 16:11 ` Prakash K. Cheemplavam
2003-11-18 18:28 ` john stultz
2003-11-18 16:15 ` Prakash K. Cheemplavam
2003-11-17 13:15 ` Felipe Alfaro Solana
2003-11-17 19:36 ` Andrew Morton
2003-11-17 19:35 ` john stultz
2003-11-18 18:56 ` Dominik Brodowski
2003-11-18 19:18 ` john stultz
-- strict thread matches above, loose matches on Subject: below --
2003-11-16 19:26 CaT
2003-11-16 20:24 ` Prakash K. Cheemplavam
2003-11-16 21:42 ` Andrew Morton
2003-11-16 22:06 ` Arnaldo Carvalho de Melo
2003-11-16 22:13 ` Andrew Morton
2003-11-16 22:18 ` CaT
2003-11-17 0:16 ` Panagiotis Papadakos
2003-11-17 2:20 ` Gawain Lynch
2003-11-17 2:49 ` Andrew Morton
2003-11-17 3:11 ` Gawain Lynch
2003-11-17 3:54 ` Gene Heskett
2003-11-17 4:19 ` Nick Piggin
2003-11-17 4:47 ` Gene Heskett
2003-11-17 5:17 ` Nick Piggin
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=1069110272.11438.2000.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=akpm@osdl.org \
--cc=cat@zip.com.au \
--cc=gawain@freda.homelinux.org \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=papadako@csd.uoc.gr \
--cc=prakashpublic@gmx.de \
--cc=s864@ii.uib.no \
--cc=schlicht@uni-mannheim.de \
/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
Powered by JetHome