From: Len Brown <lenb@kernel.org>
To: Lv Zheng <lv.zheng@intel.com>
Cc: Len Brown <len.brown@intel.com>,
Rafael J Wysocki <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: Add debugfs support for ACPICA boot time measurement.
Date: Thu, 08 Nov 2012 01:08:54 -0500 [thread overview]
Message-ID: <509B4C76.7000105@kernel.org> (raw)
In-Reply-To: <a4f15c34285624904d483e22b9b7a10c7d97fc3d.1352339077.git.lv.zheng@intel.com>
On 11/07/2012 08:49 PM, Lv Zheng wrote:
> ACPICA defines the following initialization steps that must be called to
> make ACPICA functional:
> 1. acpi_initialize_tables
> 2. acpi_initialize_subsystem
> 3. acpi_load_tables
> 4. acpi_enable_subsystem
> 5. acpi_initialize_objects
> 6. OSPM specific bus scanning
> 7. acpi_update_all_gpes
> This patch allows developers to check the execution time of such bootup
> steps through /sys/kernel/debug/acpi/acpica_init_time.
>
> The ACPICA 20121018 release measurement result is as follows:
> ========================================
> 0.000000 acpi_initialize_tables
> 0.000034 acpi_initialize_subsystem
> 0.004822 acpi_load_tables
> 0.003351 acpi_enable_subsystem
> 0.003204 acpi_initialize_objects
> 0.045082 acpi_bus_scan
> 0.000023 acpi_bus_scan_fixed
> 0.000017 acpi_update_all_gpes
> ========================================
> The left column is the execution time in timeval (sec.usec) format.
> The right column indicates the name of the initialization step.
As you've identified that 80% of the ACPI startup time goes to acpi_bus_scan(),
have you identified any ways to make acpi_bus_scan() faster?
Do these numbers vary greatly when run on different machines?
thanks,
-Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-11-08 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 1:49 [PATCH] ACPI: Add debugfs support for ACPICA boot time measurement Lv Zheng
2012-11-08 6:08 ` Len Brown [this message]
2012-11-13 2:39 ` Brown, Len
2012-11-13 7:49 ` Zheng, Lv
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=509B4C76.7000105@kernel.org \
--to=lenb@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.