[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 08 Aug 2008 16:30:14 +0200
From: Rene Herman <rene.herman@...access.nl>
To: Simon Arlott <simon@...e.lp0.eu>
CC: Alan Stern <stern@...land.harvard.edu>,
Arjan van de Ven <arjan@...radead.org>,
linux-kernel@...r.kernel.org, mingo@...e.hu,
Daniel Walker <dwalker@...sta.com>,
USB list <linux-usb@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [PATCH RFC] USB: Add HCD fastboot
On 08-08-08 13:29, Simon Arlott wrote:
> I suggest adding initcall_debug=1, it'll show how long the usb and other
> initcalls take to run. You should see the first usb device driver initcall
> take a second or two to run (without the patch). Maybe I'm just badly
> affected by having HCDs with 10 ports (of which only 4 are physically
> usable...).
>
> dmesg|grep initcall\
> |sed -e 's/.*initcall \([^ ]\+\( \(\[[^]]\+\]\)\)\?\) returned [^ ]\+ after \([^ ]\+\) secs/\4 \1/'\
> |sort -n
Thanks, but that specific expression doesn't work work me,since there's
not a single one that takes ' secs', only ' msecs'.
Here's the USB related ones here:
> [ 1.198751] initcall ehci_hcd_init+0x0/0x11 returned 0 after 123 msecs
> [ 1.818688] initcall ohci_hcd_mod_init+0x0/0x31 returned 0 after 591 msecs
> [ 2.537756] initcall usb_stor_init+0x0/0x32 returned 0 after 685 msecs
[ ... ]
> [ 2.619477] initcall hid_init+0x0/0x3 returned 0 after 0 msecs
> [ 2.629667] initcall hid_init+0x0/0x3e returned 0 after 9 msecs
685 isn't nice but better then 2000...
Rene.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists