From: Alan Stern <stern@rowland.harvard.edu>
To: Paul Menzel <pmenzel+linux-pci@molgen.mpg.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
<linux-usb@vger.kernel.org>
Subject: Re: `pci_apply_final_quirks()` taking half a second
Date: Mon, 1 Jan 2018 10:47:19 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1801011041420.5613-100000@netrider.rowland.org> (raw)
In-Reply-To: <92dff466-d0a5-b30c-4d47-48584fac579e@molgen.mpg.de>
On Mon, 1 Jan 2018, Paul Menzel wrote:
> > So they are OHCI controllers. You could add some debugging statements
> > to quirk_usb_handoff_ohci() to try and locate the part that's taking so
> > long.
>
> As you suggested debugging statements, I guess the Linux kernel doesn’t
> offer other ways to instrument functions without modifying the source code.
It does. Look into ftrace, for example. However, ftrace only provides
tracing at the level of function calls (hence the name -- "ftrace" for
"function trace"), not for individual statements within a function.
There are other facilities as well, but none of them are likely to help
here.
> Is it possible to only rebuild the module somehow or is the early
> handoff stuff not a module?
It is not a module.
> > It's also worth mentioning that the same source file contains lots of
> > special-case code for AMD and ASmedia hardware. I don't know whether
> > any of it is involved in the long time delays you are seeing, however.
>
> Thank you for already looking into this. I haven’t had to time to read
> the commit messages, which might shed some light into the reasoning.
Good luck!
Alan Stern
next prev parent reply other threads:[~2018-01-01 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 21:07 `pci_apply_final_quirks()` taking half a second Paul Menzel
2017-04-08 15:41 ` Bjorn Helgaas
2017-04-08 17:00 ` David Woodhouse
2017-04-08 19:06 ` Bjorn Helgaas
2017-05-03 18:42 ` Andy Shevchenko
2017-12-26 15:55 ` Paul Menzel
2017-12-28 21:27 ` Bjorn Helgaas
2017-12-29 16:14 ` Alan Stern
2017-12-31 7:18 ` Paul Menzel
2017-12-31 21:16 ` Alan Stern
2018-01-01 10:21 ` Paul Menzel
2018-01-01 15:47 ` Alan Stern [this message]
2018-06-24 16:49 ` `quirk_usb_handoff_ohci` takes over 73 ms (twice) on AMD system (was: `pci_apply_final_quirks()` taking half a second) Paul Menzel
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=Pine.LNX.4.44L0.1801011041420.5613-100000@netrider.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=andy.shevchenko@gmail.com \
--cc=dwmw2@infradead.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmenzel+linux-pci@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;
as well as URLs for NNTP newsgroup(s).