public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: acpi_battery_init() boot speed
Date: Thu, 16 Dec 2010 23:31:18 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1012162329360.20940@x980> (raw)
In-Reply-To: <20101215205845.3e13fad2@infradead.org>


> make it a module, and run "perf top" while in an other terminal you do
> 
> while :; do modprobe acpi_battery ; rmmod acpi_battery  ; done

----------------------------------------------------------------------
   PerfTop:     747 irqs/sec  kernel:94.5%  exact:  0.0% [1000Hz cycles],  
(all, 2 CPUs)
----------------------------------------------------------------------

             samples  pcnt function            DSO
             _______ _____ ___________________ _______________________

             2502.00 28.4% intel_idle          [kernel.kallsyms]      
              802.00  9.1% acpi_os_read_port   [kernel.kallsyms]      
              735.00  8.4% read_hpet           [kernel.kallsyms]      
              559.00  6.4% check_poison_obj    [kernel.kallsyms]      
              286.00  3.3% acpi_ec_gpe_handler [kernel.kallsyms]      
              208.00  2.4% cache_free_debugche [kernel.kallsyms]      
              200.00  2.3% cache_alloc_debugch [kernel.kallsyms]      
              169.00  1.9% kmem_cache_alloc    [kernel.kallsyms]      
              138.00  1.6% acpi_debug_print    [kernel.kallsyms]      
               90.00  1.0% hpet_next_event     [kernel.kallsyms]      
               88.00  1.0% kmem_cache_free     [kernel.kallsyms]      
               83.00  0.9% acpi_os_write_port  [kernel.kallsyms]      
               74.00  0.8% acpi_ps_parse_loop  [kernel.kallsyms]      
               72.00  0.8% find_busiest_group  [kernel.kallsyms]      
               72.00  0.8% schedule            [kernel.kallsyms]      
               58.00  0.7% _raw_spin_lock_irqs [kernel.kallsyms]      
               58.00  0.7% acpi_ps_get_opcode_ [kernel.kallsyms]      
               56.00  0.6% advance_transaction [kernel.kallsyms]      
               54.00  0.6% menu_select         [kernel.kallsyms]      
               52.00  0.6% __might_sleep       [kernel.kallsyms]      
               47.00  0.5% ktime_get           [kernel.kallsyms]      
               41.00  0.5% __virt_addr_valid   [kernel.kallsyms]      
               38.00  0.4% start_transaction   [kernel.kallsyms]      
               38.00  0.4% acpi_ec_transaction [kernel.kallsyms]      
               36.00  0.4% dbg_redzone2        [kernel.kallsyms]      
               36.00  0.4% _raw_spin_unlock_ir [kernel.kallsyms]      
               35.00  0.4% tick_nohz_stop_sche [kernel.kallsyms]      
               33.00  0.4% acpi_ps_complete_op [kernel.kallsyms]      
               32.00  0.4% sched_clock         [kernel.kallsyms]      
               32.00  0.4% getnstimeofday      [kernel.kallsyms]      
               32.00  0.4% __switch_to         [kernel.kallsyms]      
               31.00  0.4% acpi_ds_exec_end_op [kernel.kallsyms]      
               31.00  0.4% ec_check_ibf0       [kernel.kallsyms]      
               31.00  0.4% irq_entries_start   [kernel.kallsyms]      
               30.00  0.3% acpi_hw_read        [kernel.kallsyms]      
               30.00  0.3% acpi_ev_gpe_detect  [kernel.kallsyms]      
               29.00  0.3% acpi_ec_transaction [kernel.kallsyms]      
               28.00  0.3% acpi_ut_update_obje [kernel.kallsyms]      
               27.00  0.3% acpi_ut_update_ref_ [kernel.kallsyms]      
               26.00  0.3% acpi_hw_validate_io [kernel.kallsyms]      
               25.00  0.3% acpi_hw_read_port   [kernel.kallsyms]      
               24.00  0.3% find_symbol_in_sect [kernel.kallsyms]      
               24.00  0.3% __GI___strcmp_ssse3 /lib64/libc-2.12.90.so 
               23.00  0.3% __phys_addr         [kernel.kallsyms]      
               23.00  0.3% acpi_ex_resolve_ope [kernel.kallsyms]      
               21.00  0.2% select_task_rq_fair [kernel.kallsyms]      
               21.00  0.2% acpi_hw_validate_re [kernel.kallsyms]      
               21.00  0.2% enqueue_task_fair   [kernel.kallsyms]      
               20.00  0.2% cpuidle_idle_call   [kernel.kallsyms]      
               19.00  0.2% find_next_bit       [kernel.kallsyms]      
               19.00  0.2% ns_to_timeval       [kernel.kallsyms]      
               19.00  0.2% _raw_spin_lock      [kernel.kallsyms]      
               19.00  0.2% acpi_ut_allocate_ob [kernel.kallsyms]      
               19.00  0.2% acpi_ut_create_gene [kernel.kallsyms]      
               19.00  0.2% g_hash_table_lookup libglib-2.0.so.0.2600.0
               18.00  0.2% sched_clock_local   [kernel.kallsyms] 

  reply	other threads:[~2010-12-17  4:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15  8:13 acpi_battery_init() boot speed Len Brown
2010-12-15  8:15 ` Len Brown
2010-12-15 11:00 ` Arjan van de Ven
2010-12-15 20:27   ` Len Brown
2010-12-16  4:58     ` Arjan van de Ven
2010-12-17  4:31       ` Len Brown [this message]
2010-12-17  8:46   ` Len Brown
2010-12-17 16:02     ` Arjan van de Ven

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=alpine.LFD.2.00.1012162329360.20940@x980 \
    --to=lenb@kernel.org \
    --cc=arjan@infradead.org \
    --cc=linux-acpi@vger.kernel.org \
    /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