>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]] On Behalf Of
>Kenneth Parrish
>Sent: Wednesday, June 08, 2005 5:15 PM
>To: [email protected]
>Subject: Re: [ACPI] acpi_processor_set_power_policy
>
>-=> Kenneth Parrish wrote to All <=-
>
> KP> SEEN-BY: 8/1 2 2003
> KP> PATH: 8/2003 1 2
> KP> MSGID: 8:8/2003 122ea9cd
> KP> TZUTC: -0600
> KP> CHARSET: PC-8
> KP> From: Kenneth Parrish <[email protected]>
>
> KP> # readprofile -r ; sleep 1 ; readprofile -m /boot/System.map
> | sort -nr
>
> KP> 527 total 0.0003
> KP> 502 acpi_processor_set_power_policy 2.6989
> KP> 7 sort 0.0208
> KP> 7 release_task 0.0208
> KP> 4 zone_watermark_ok 0.0208
> KP> 3 do_page_fault 0.0021
> KP> 1 unmap_page_range 0.0057
> KP> 1 show_free_areas 0.0013
> KP> 1 do_file_page 0.0048
> KP> 1 buffered_rmqueue 0.0020
>
> KP> Should acpi_processor_set_power_policy be called this often?
>
> KP> Kernel: 2.6.12-rc5-git9 # define HZ 500
> KP> <include/asm-i386/param.h> Computer: Cyrix MII and VIA MVP3,
> KP> e-machines '99 dmesg.. Kernel command line:
> KP> BOOT_IMAGE=2.6.12-rc5-git9 ro root=301 clock=tsc elevator=
> KP> deadline lpj=376832 profile=2
> KP> kernel profiling enabled (shift: 2)
>
> KP> More information and at request.
>
> KP> ... A: 6-1/2" x 6-1/2" x 2" Q: How big is the Mac Mini?
> KP> -+- MultiMail/Linux v0.46 [currently BlueWave packet type]
> KP> -
> KP> To unsubscribe from this list: send the line "unsubscribe
> KP> linux-kernel" in the body of a message to
> KP> [email protected] More majordomo info at
> KP> http://vger.kernel.org/majordomo-info.html Please read the
> KP> FAQ at http://www.tux.org/lkml/
>
> KP> --- BBBS/NT v4.01 Flag-5
> KP> * Origin: FamilyNet Sponsored by
> KP> http://www.christian-wellness.net (8:8/2003)
>
>I noticed the subject function appears in drivers/acpi/processor_idle.c
>and tried a couple of things. Look OK? comments on the
>[misguided?] patch?
>:-)
Are you sure that this patch is causing this difference with
acpi_processor_set_power_policy() calls.
Looking at the code, set_power_policy() is only called at init time
and _CST change interrupt. So, I am not sure how these changes are
affecting it.
One guess.. System.map used in your original data may be wrong for
that kernel, which might have caused it to point at set_power_policy()
in place of acpi_procesor_idle()....
Thanks,
Venki
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
