From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: Slow booting on x15
Date: Fri, 25 Sep 2020 14:58:17 +0300 [thread overview]
Message-ID: <20200925115817.GB3933@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200925115147.GM9471@atomide.com>
On Fri, Sep 25, 2020 at 02:51:47PM +0300, Tony Lindgren wrote:
> * Laurent Pinchart <laurent.pinchart@ideasonboard.com> [200924 13:31]:
> > Hi Tony,
> >
> > On Thu, Sep 24, 2020 at 09:08:26AM +0300, Tony Lindgren wrote:
> > > * Tomi Valkeinen <tomi.valkeinen@ti.com> [200924 06:05]:
> > > > On 24/09/2020 08:53, Tony Lindgren wrote:
> > > > >>>>> On Fri, Sep 18, 2020 at 06:25:02PM +0300, Tomi Valkeinen wrote:
> > > > >>>>>> v5.9-rc5
> > > > >>>>>> [ 0.706165] cpuidle: using governor menu
> > > > >>>>>> [ 6.761812] No ATAGs?
> > > > >>>>>>
> > > > >>>>>> [ 19.522536] Run /sbin/init as init process
> > > > >
> > > > > Hmm v5.9-rc1 here with NFSroot shows this for me:
> > > > >
> > > > > [ 11.704511] Run /sbin/init as init process
> > > > >
> > > > > And v5.9-rc6 shows:
> > > > >
> > > > > [ 13.120913] Run /sbin/init as init process
> > > > >
> > > > > With at least two seconds spent on waiting for Ethernet PHY to
> > > > > negotiate the speed. This is with omap2plus_defconfig.
> > > >
> > > > I'm also using nfsroot, so I didn't put too much weight on the "Run /sbin/init as init process"
> > > > line, as it could also be caused the network or the nfs server. But the "No ATAGs" lines already
> > > > show an increase from 0.8s to 6.7s from v5.7 to v5.9-rc5.
> >
> > Yes, that's the main issue.
> >
> > > That's strange, I'm seeing this with v5.9-rc6:
> > >
> > > [ 2.357585] No ATAGs?
> >
> > What's your test platform ?
>
> This is from beagle x15. I wonder how Tomi is seeing over six seconds
> at that point though while I'm seeing two something.
And I see 10s on the same platform.
> > Still, 1.5s spent there is quite a lot.
>
> Probably that's when module_init runs and we probe almost everything.
> Might be worth profiling to see if we can optimize out some full dtb
> tree searches for example.
As far as I can tell, module_init() runs later than that. If we probed
everything there would be lots of messages printed during that period of
time.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2020-09-25 11:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 15:25 Slow booting on x15 Tomi Valkeinen
2020-09-18 15:58 ` Laurent Pinchart
2020-09-23 7:07 ` Tony Lindgren
2020-09-23 11:13 ` Laurent Pinchart
2020-09-24 5:42 ` Tony Lindgren
2020-09-24 5:53 ` Tony Lindgren
2020-09-24 6:04 ` Tomi Valkeinen
2020-09-24 6:08 ` Tony Lindgren
2020-09-24 13:30 ` Laurent Pinchart
2020-09-25 11:51 ` Tony Lindgren
2020-09-25 11:58 ` Laurent Pinchart [this message]
2020-09-30 5:20 ` Tony Lindgren
2020-09-30 12:41 ` Peter Ujfalusi
2020-10-01 7:53 ` Tony Lindgren
2020-10-01 8:17 ` Tony Lindgren
2020-10-01 8:22 ` Laurent Pinchart
2020-10-01 12:56 ` Grygorii Strashko
2020-10-01 13:11 ` Geert Uytterhoeven
2020-10-01 13:49 ` Grygorii Strashko
2020-10-01 18:24 ` Saravana Kannan
2020-10-01 19:43 ` Grygorii Strashko
2020-10-01 22:22 ` Saravana Kannan
2020-10-01 22:30 ` Saravana Kannan
2020-10-01 22:38 ` Laurent Pinchart
2020-10-01 22:44 ` Saravana Kannan
2020-10-01 22:59 ` [PATCH v1] of: platform: Batch fwnode parsing in the init_machine() path Saravana Kannan
2020-10-01 23:19 ` Laurent Pinchart
2020-10-02 11:40 ` Grygorii Strashko
2020-10-02 15:03 ` Grygorii Strashko
2020-10-02 17:48 ` Saravana Kannan
2020-10-02 18:11 ` Grygorii Strashko
2020-10-02 14:07 ` Rob Herring
2020-10-02 17:51 ` Saravana Kannan
2020-10-02 17:54 ` Laurent Pinchart
2020-10-02 17:58 ` Saravana Kannan
2020-10-02 18:27 ` Laurent Pinchart
2020-10-02 18:35 ` Grygorii Strashko
2020-10-02 19:56 ` Saravana Kannan
2020-10-03 0:13 ` Laurent Pinchart
2020-10-27 3:29 ` Saravana Kannan
2020-10-28 7:34 ` Tomi Valkeinen
2020-10-02 20:29 ` Rob Herring
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=20200925115817.GB3933@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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 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).