From: Bruno Thomsen <bth@kamstrup.com>
To: "Jürgen Borleis" <jbe@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] prelink: first boot warning
Date: Fri, 19 Jun 2015 10:41:17 +0000 [thread overview]
Message-ID: <915054555B5659448ACF8A70E114824D01A4C03B54@Exchange2010.kamstrup.dk> (raw)
In-Reply-To: <201506181508.32817.jbe@pengutronix.de>
Hi Juergen,
> > Running prelink with rc.once.d causes a first boot stall of about 2
> > minutes on Freescale i.MX28 454MHz ARM9 processor.
> > This can be expensive if first device boot is during product
> > manufacturing (assembly, programming, configuration, test).
>
> With Using a recent linker the prelink becomes redundant. It is already done when the linker hash-style it set to "gnu" (which is the default in a recent PTXdist).
> Or did you still see improvements with or without the pre-link step and that's why you are still using this feature?
The feature was enabled by mistake during a ptxdist upgrade from 2012.04 (TQ BSP 0101) to 2013.12 (TQ BSP 0109).
Normally I cherry-pick rule upgrades rather than doing full ptxdist upgrade, since it's easier to maintain auto build servers, if they only need to do a source checkout.
We don't see any noticeable app start improvements. But disabling prelink result in a significant lower product production time.
/Bruno
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-06-19 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 12:51 Bruno Thomsen
2015-06-18 13:08 ` Jürgen Borleis
2015-06-19 10:41 ` Bruno Thomsen [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=915054555B5659448ACF8A70E114824D01A4C03B54@Exchange2010.kamstrup.dk \
--to=bth@kamstrup.com \
--cc=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.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