public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
Cc: john stultz <johnstul@us.ibm.com>,
	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: Tue, 18 Nov 2003 17:15:09 +0100	[thread overview]
Message-ID: <3FBA458D.2010803@gmx.de> (raw)
In-Reply-To: <3FBA1D78.8060502@gmx.de>

Prakash K. Cheemplavam wrote:

 >>
 >> 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.
 >
 >
 >
 >
 > I now tried the second one and it seems to work, tough I am not sure 
whether the performance is as good as APCI timer deavt. It seems that 
now CPU Hz is not shown anymore. Have a look at my dmesg:
 >
 >
 > Linux version 2.6.0-test9-love3 (root@tachyon) (gcc-Version 3.3.2 
20031022 (Gentoo Linux 3.3.2-r2, propolice)) #16 Tue Nov 18 13:54:04 CET 
2003
 > BIOS-provided physical RAM map:
 >  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
 >  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
 >  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 >  BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
 >  BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
 >  BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
 >  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 >  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 >  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
 > 127MB HIGHMEM available.
 > 896MB LOWMEM available.
 > On node 0 totalpages: 262128
 >   DMA zone: 4096 pages, LIFO batch:1
 >   Normal zone: 225280 pages, LIFO batch:16
 >   HighMem zone: 32752 pages, LIFO batch:7
 > DMI 2.2 present.
 > ACPI: RSDP (v000 Nvidia                                    ) @ 0x000f6b60
 > ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff3000
 > ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff3040
 > ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff79c0
 > ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
 > ACPI: PM-Timer IO Port: 0x4008
 > Building zonelist for node : 0
 > Kernel command line: root=/dev/hde6 hdg=none vga=0x51A 
video=vesa:mtrr,ywrap elevator=cfq
 > ide_setup: hdg=none
 > current: c0499a60
 > current->thread_info: c0528000
 > Initializing CPU#0
 > PID hash table entries: 4096 (order 12: 32768 bytes)
 > Using <NULL> for high-res timesource


[snip]

So I deactivated the PM timer again and my computer is much faster 
again. Haven prime in the background taking 100% doesn't noticeable 
affect deskop performance. But I think I know where the problem lies:

current: c0499a60
current->thread_info: c0528000
Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 2004.698 MHz processor.
Using tsc for high-res timesource


In above dmesg you can see that nothing was used as timesource, but here 
in current dmesg tsc is used. Is this normal or a bug? Need I pass a 
kernel paramtere when pm timer is enbaled?

bye

Prakash



  parent reply	other threads:[~2003-11-18 16:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 12:11 Terrible interactivity with 2.6.0-t9-mm3 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
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 [this message]
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=3FBA458D.2010803@gmx.de \
    --to=prakashpublic@gmx.de \
    --cc=akpm@osdl.org \
    --cc=cat@zip.com.au \
    --cc=gawain@freda.homelinux.org \
    --cc=gene.heskett@verizon.net \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=papadako@csd.uoc.gr \
    --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