From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Lee Jones <lee@kernel.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: `intel_lpss_pci_driver_init` takes 23.8 ms
Date: Thu, 14 Mar 2024 15:30:37 +0200 [thread overview]
Message-ID: <ZfL7_Uuh0EQrptNG@smile.fi.intel.com> (raw)
In-Reply-To: <49d0a968-7570-43ac-963c-47b9c6dcc353@molgen.mpg.de>
On Sun, Feb 11, 2024 at 08:38:15PM +0100, Paul Menzel wrote:
> Am 08.02.24 um 18:33 schrieb Andy Shevchenko:
> > On Thu, Feb 08, 2024 at 08:59:28AM +0000, Lee Jones wrote:
> > > On Tue, 06 Feb 2024, Paul Menzel wrote:
...
> > > > On the Dell XPS 13 9360 and Linux 6.8-rc3+, `intel_lpss_pci_driver_init()`
> > > > takes 23.8 ms, making it one of Linux’ longer init functions on this device:
> >
> > Does it mean on the previous releases it was different?
> > I mean is it a regression or always was like this?
Okay.
...
> but this seems to have a big affect on ACPI/ASL operations, and execution
> time increases to 125 ms. This breaks down to
>
> 1. `i2c_acpi_find_bus_speed()` (96.985 ms @ 3.008753), where
> `acpi_walk_namespace()` takes this time.
> 2. `i2c_dw_probe_master()` (27.161 ms @ 3.105964) →
> i2c_add_numbered_adapter()` → `i2c_add_adapter()` → `i2c_register_adapter()`
> → `i2c_acpi_register_devices()` → `acpi_ns_walk_namespace()` (24.178 ms @
> 3.108927)
>
> No idea if this is a red herring, and the long time is actually do to
> something else.
Might be related https://github.com/acpica/acpica/pull/897
Wonder if it helps you anyhow.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-03-14 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 21:08 `intel_lpss_pci_driver_init` takes 23.8 ms Paul Menzel
2024-02-08 8:59 ` Lee Jones
2024-02-08 17:33 ` Andy Shevchenko
2024-02-11 19:38 ` Paul Menzel
2024-03-14 13:30 ` Andy Shevchenko [this message]
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=ZfL7_Uuh0EQrptNG@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.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