From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] Boottime: A tool for automatic measurement of kernel/bootloader boot time
Date: Thu, 15 Nov 2012 18:31:43 +0100 [thread overview]
Message-ID: <CACRpkdb+hKL0mZLa=Kusoh9r5V6rukmTdLmxc2erwhA6-YLZjg@mail.gmail.com> (raw)
In-Reply-To: <201211151225.31066.arnd@arndb.de>
On Thu, Nov 15, 2012 at 1:25 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Thursday 15 November 2012, Lee Jones wrote:
>>
>> > > +/* for automatic boot timing testcases */
>> > > +#define ATAG_BOOTTIME 0x41000403
>> > Where can I refer this ATAG usage? can you point out the reference URL
>> > or patches?
>>
>> I assumed this would be in Mainline u-boot, but apparently not.
>> On closer inspection of the internal ST-Ericsson u-boot, this
>> functionality appears to be provided by patches which currently
>> exist as delta. So in essence, the bootloader you use will have
>> to be patched in a similar way for you to retrieve information
>> surrounding bootloader boot times.
>>
>> And there was me thinking it was magic. ;)
>>
>
> And since we're moving away from ATAG on ux500 towards DT, it won't
> even work in the future. How essential is this part for the operation
> of your code?
To be fun we need some mechanism to pass this info from the
boot loader to the kernel.
I think most bootloaders are already dynamically altering their
device trees to put in things like memory size etc so this would
probably be done the same way: a standard binding like for
everything else, then put the data in there.
I don't know if Lee has a modifiable U-boot to try out such
concepts on though?
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-11-15 17:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 10:04 [PATCH 0/2] Boottime: measure bootloader and kernel bootup time Lee Jones
2012-11-15 10:04 ` [PATCH 1/2] Boottime: A tool for automatic measurement of kernel/bootloader boot time Lee Jones
2012-11-15 10:16 ` Kyungmin Park
2012-11-15 11:25 ` Lee Jones
2012-11-15 12:25 ` Arnd Bergmann
2012-11-15 17:31 ` Linus Walleij [this message]
2012-11-20 16:16 ` Lee Jones
2012-11-29 20:35 ` Simon Glass
2012-11-30 8:21 ` Lee Jones
2012-11-15 13:52 ` Andrew Murray
2012-11-15 14:37 ` Lee Jones
2012-11-15 10:04 ` [PATCH 2/2] clocksource: clksrc-dbx500-prcmu: Add boottime support Lee Jones
2012-11-15 10:15 ` [PATCH 0/2] Boottime: measure bootloader and kernel bootup time Jean-Christophe PLAGNIOL-VILLARD
2012-11-15 10:35 ` Lee Jones
2012-11-15 10:57 ` Jean-Christophe PLAGNIOL-VILLARD
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='CACRpkdb+hKL0mZLa=Kusoh9r5V6rukmTdLmxc2erwhA6-YLZjg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--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).