From: Lee Jones <lee.jones@linaro.org>
To: Nishanth Menon <nm@ti.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
linus.walleij@stericsson.com,
Jonas Aaberg <jonas.aberg@stericsson.com>,
Will Deacon <will.deacon@arm.com>,
arnd@arndb.de,
Mian Yousaf Kaukab <mian.yousaf.kaukab@stericsson.com>,
dmurphy@ti.com
Subject: Re: [PATCH] Boottime: A tool for automatic measurement of kernel/bootloader boot time
Date: Fri, 12 Oct 2012 10:37:07 +0100 [thread overview]
Message-ID: <20121012093707.GC12567@gmail.com> (raw)
In-Reply-To: <20121011201735.GA15313@kahuna>
On Thu, 11 Oct 2012, Nishanth Menon wrote:
> On 15:42-20121011, Lee Jones wrote:
> > From: Jonas Aaberg <jonas.aberg@stericsson.com>
> >
> > The overhead is very low and the results will be found under
> > sysfs/bootime, as well as detailed results in debugfs under
> > boottime/. The bootgraph* files are compatible with
> > scripts/bootgraph.pl. The reason for this patch is to provide
> > data (sysfs/boottime) suitable for automatic testcases as
> > well as help for developers to reduce the boot time (debugfs).
> Tried master:
> 250d8 Merge branch 'i2c-embedded/for-next' of git://git.pengutronix.de/git/wsa/linux
> and v3.6-rc7
> with omap2plus_defconfig + CONFIG_BOOTTIME enabled:
>
> init/boottime.c:47:9: error: ‘cpu_usage_stat’ defined as wrong kind of tag
> init/boottime.c:47:24: error: array type has incomplete element type
> init/boottime.c: In function ‘boottime_mark_core’:
> init/boottime.c:127:313: error: ‘struct kernel_stat’ has no member named ‘cpustat’
> init/boottime.c:128:311: error: ‘struct kernel_stat’ has no member named ‘cpustat’
> init/boottime.c:129:313: error: ‘struct kernel_stat’ has no member named ‘cpustat’
> init/boottime.c:130:310: error: ‘struct kernel_stat’ has no member named ‘cpustat’
>
> if it depended on some other patch or a specific maintainer branch,
> it was'nt clear.
No, this is completely my fault.
There are added dependencies and fixups that I missed.
I'll fixup and resubmit.
Unfortunately, there are now other authors involved, so I need to
seek permission before squashing them in. Please bear with me.
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2012-10-12 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 14:42 [PATCH] Boottime: A tool for automatic measurement of kernel/bootloader boot time Lee Jones
2012-10-11 15:24 ` Christian Gmeiner
2012-10-11 15:36 ` Lee Jones
2012-10-11 20:17 ` Nishanth Menon
2012-10-12 9:37 ` Lee Jones [this message]
2012-10-12 9:51 ` Lee Jones
2012-10-12 13:35 ` Dan Murphy
2012-10-12 13:45 ` Lee Jones
2012-10-12 13:48 ` Russell King - ARM Linux
2012-10-12 13:53 ` Arnd Bergmann
2012-10-12 14:01 ` Lee Jones
2012-10-12 16:36 ` Dan Murphy
2012-10-12 16:42 ` Lee Jones
2012-10-15 15:52 ` Dan Murphy
2012-10-16 7:34 ` Lee Jones
2012-10-23 7:19 ` Lee Jones
2013-06-09 8:17 ` Steve Liu
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=20121012093707.GC12567@gmail.com \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=dmurphy@ti.com \
--cc=jonas.aberg@stericsson.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mian.yousaf.kaukab@stericsson.com \
--cc=nm@ti.com \
--cc=will.deacon@arm.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