From: juri.lelli@arm.com (Juri Lelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 0/4] CPUs capacity information for heterogeneous systems
Date: Wed, 20 Jan 2016 10:22:37 +0000 [thread overview]
Message-ID: <20160120102237.GN8573@e106622-lin> (raw)
In-Reply-To: <20160119211049.GX6588@sirena.org.uk>
On 19/01/16 21:10, Mark Brown wrote:
> On Tue, Jan 19, 2016 at 11:48:15AM -0800, Steve Muckle wrote:
> > On 01/19/2016 06:29 AM, Juri Lelli wrote:
>
> > > I'm generally seeing ~1sec increase in boot time for 1 and practically
> > > no difference for 2 (even after having added patches that provide
> > > runtime performance improvements).
>
> > One second is considerable IMO. Aside from the general desire to have
> > shorter boot times on any platform there are environments like
> > automotive where boot time is critical.
>
> Yeah, definitely. Is this actually blocking boot and if so can we
> arrange to do this in parallel with other activity (with likely knock on
> effects on reproducibility...)?
No, this goes in parallel. That's also showed by the fact that the
benchmarking thing itself usually takes more that 1 sec, but it seems to
impact for that amount of time only.
next prev parent reply other threads:[~2016-01-20 10:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 14:09 [RFC PATCH v2 0/4] CPUs capacity information for heterogeneous systems Juri Lelli
2016-01-08 14:09 ` [RFC PATCH v2 1/4] ARM: initialize cpu_scale to its default Juri Lelli
2016-01-08 14:09 ` [RFC PATCH v2 2/4] drivers/cpufreq: implement init_cpu_capacity_default() Juri Lelli
2016-01-08 14:09 ` [RFC PATCH v2 3/4] arm: Enable dynamic CPU capacity initialization Juri Lelli
2016-01-08 14:09 ` [RFC PATCH v2 4/4] arm64: " Juri Lelli
2016-01-15 18:01 ` [RFC PATCH v2 0/4] CPUs capacity information for heterogeneous systems Mark Brown
2016-01-18 15:01 ` Juri Lelli
2016-01-15 19:50 ` Steve Muckle
2016-01-18 15:13 ` Juri Lelli
2016-01-18 16:13 ` Vincent Guittot
2016-01-18 16:30 ` Juri Lelli
2016-01-18 16:42 ` Vincent Guittot
2016-01-18 17:08 ` Juri Lelli
2016-01-18 17:23 ` Vincent Guittot
2016-01-19 10:59 ` Catalin Marinas
2016-01-19 11:23 ` Juri Lelli
2016-01-19 14:29 ` Juri Lelli
2016-01-19 19:48 ` Steve Muckle
2016-01-19 21:10 ` Mark Brown
2016-01-20 10:22 ` Juri Lelli [this message]
2016-01-18 19:25 ` Steve Muckle
2016-01-19 15:05 ` Peter Zijlstra
2016-01-19 17:50 ` Mark Brown
2016-01-20 10:25 ` Juri Lelli
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=20160120102237.GN8573@e106622-lin \
--to=juri.lelli@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).